Davis Versions Save

🗓 A simple, fully translatable admin interface for sabre/dav based on Symfony 5 and Bootstrap 5, initially inspired by Baïkal.

v4.4.3

3 weeks ago

This is a minor fix addressing Docker improvements and other things

What's Changed

How to upgrade

Nothing if you're on v4.4.2

Full Changelog: https://github.com/tchapi/davis/compare/v4.4.2...v4.4.3

v4.4.2

2 months ago

What's Changed

  • Ability to use Webdav home directories in #143
  • Various Docker improvements
  • Fix PostgreSQL default encoding in #153
  • Allow setting Symfony's dotenv path in #156

How to upgrade

Nothing. There is a new WEBDAV_HOMES_DIR env var (default to an empty string, disabling the home directories), check the README for more information.

Thanks @Ramblurr, @AkselMeola and @de-es for their help

Full Changelog: https://github.com/tchapi/davis/compare/v4.4.1...v4.4.2

v4.4.1

4 months ago

What's Changed

How to upgrade

There's nothing much to do, but you can:

  1. Add the (optional) APP_TIMEZONE env var if you want to enforce the timezone. By default, timezone is not enforced (which should yield the same behavior as before).

[!TIP] If you pass the timezone in a Docker env, take care of not including quotes " around the value of the timezone, as they will be passed down to Davis which will result in a bad timezone id. (See the example Docker env file for reference)

  1. If you use an external auth provider (such as Authelia) in front of Davis, you can now disable the baked-in auth easily with the ADMIN_AUTH_BYPASS env var (set it to true). By default, nothing changes from the previous release.

💁🏼‍♂️ Also, if you're coming from a release before 4.4.0, please do not forget to run the migration process below

[!NOTE] If you encounter the log The parameter "timezone" must be defined. when doing composer install, it means that your cache (from the previous version) is obsolete and Symfony does not manage to clear it. You can do:

rm -rf ./var/cache. # in the Davis application folder

to clean things up. The subsequent composer install will rebuild the cache from scratch and everything should work as expected.

Thanks @MuratovAS for the challenge on auth mechanisms

Full Changelog: https://github.com/tchapi/davis/compare/v4.4.0...v4.4.1

v4.4.0

5 months ago

What's Changed

How to migrate your database

[!TIP] The added migration will only make changes if you're on MySQL; it's expected, you can ignore if you're using PostgreSQL or SQLite

0. Back up your database

This is a safety precaution in case you end up messing with a migration or the database in general. It's highly recommended, even if you know exactly what you're doing.

1. Update the code and migrate

You can now update the code (either directly or get the up to date container), and then run the remaining migrations with:

bin/console doctrine:migrations:migrate --allow-no-migration

[!NOTE] Some migrations are for PostgreSQL, some for MySQL, so it's perfectly normal if you always have a "New" migration that is skipped, and if you're not at the latest one.

Full Changelog: https://github.com/tchapi/davis/compare/v4.3.0...v4.4.0

v4.3.0

6 months ago

What's Changed

💁🏼‍♂️ If you're coming from a release before 4.2.0, please do not forget to run the migration process below

How to migrate your database

[!WARNING] While not exactly breaking, you have to update the database schema to have the correct column type. Follow the instructions below.

0. Back up your database

This is a safety precaution in case you end up messing with a migration or the database in general. It's highly recommended, even if you know exactly what you're doing.

1. Update the code and migrate

You can now update the code (either directly or get the up to date container), and then run the remaining migrations with:

bin/console doctrine:migrations:migrate

[!NOTE] Some migrations are for PostgreSQL, some for MySQL, so it's perfectly normal if you always have a "New" migration that is skipped, and if you're not at the latest one.

Full Changelog: https://github.com/tchapi/davis/compare/v4.2.1...v4.3.0

v4.2.1

6 months ago

[!WARNING] THIS RELEASE IS YANKED. Please update to 4.3.0 directly, following the migration process of 4.2.0

What's Changed

  • Fix a missing import in AddressBook controller

Full Changelog: https://github.com/tchapi/davis/compare/v4.2.0...v4.2.1

v4.2.0

6 months ago

[!WARNING] THIS RELEASE IS YANKED. Please update to 4.3.0 directly, following the migration process below

What's Changed

  • Feature: allow public calendars in https://github.com/tchapi/davis/pull/105
    • Thank you @1Luc1 for your support
  • Fix: remove sensitive logs in #116
    • Thanks @mpflanzer for the tests
  • Fix: change remaining columns to TEXT instead of BLOB in #111
    • Thanks @spammads and @thelittleblackbird for your help 🙏🏼
  • Update to sabre/dav 4.5.0

How to migrate your database

[!WARNING] While not exactly breaking, you have to update the database schema to have the correct column type. Follow the instructions below.

0. Back up your database

This is a safety precaution in case you end up messing with a migration or the database in general. It's highly recommended, even if you know exactly what you're doing.

1. Update the code and migrate

You can now update the code (either directly or get the up to date container), and then run the remaining migrations with:

bin/console doctrine:migrations:migrate

[!NOTE] Some migrations are for PostgreSQL, some for MySQL, so it's perfectly normal if you always have a "New" migration that is skipped, and if you're not at the latest one.

Full Changelog: https://github.com/tchapi/davis/compare/v4.1.0...v4.2.0

v4.1.0

7 months ago

What's Changed

Full Changelog: https://github.com/tchapi/davis/compare/v4.0.0...v4.1.0

v4.0.0

9 months ago

What's Changed

[!WARNING]

:warning: This release drops support for PHP < 8.0 :warning:

New Contributors

Full Changelog: https://github.com/tchapi/davis/compare/v3.3.0...v4.0.0

v3.3.1

9 months ago

What's Changed

Full Changelog: https://github.com/tchapi/davis/compare/v3.3.0...v3.3.1