davis

πŸ—“ A simple, fully translatable admin interface for sabre/dav based on Symfony 5 and Bootstrap 5, initially inspired by BaΓ―kal.

MIT License

Stars
292
View Code on GitHub Visit Website
Ecosystems: Bootstrap

Bot releases are hidden (Show)

davis - v5.0.1-rc Latest Release

Published by tchapi 3 months ago

[!WARNING]
This is a pre-release pending further testing

What's Changed

  • Fix a bug when trying to load the profiler in production mode

This is a major update of Symfony to the 7.0 version, but including no new features.

⚠️ This release drops PHP 8.0 and PHP 8.1 support

Full Changelog: https://github.com/tchapi/davis/compare/v4.4.4...v5.0.1-rc

davis - v5.0.0-rc

Published by tchapi 3 months ago

[!WARNING]
This is a pre-release pending further testing

What's Changed

This is a major update of Symfony to the 7.0 version, but including no new features.

⚠️ This release drops PHP 8.0 and PHP 8.1 support

Full Changelog: https://github.com/tchapi/davis/compare/v4.4.4...v5.0.0-rc

davis - v4.4.4

Published by tchapi 3 months ago

This is a minor fix addressing Docker improvements and other things

What's Changed

This release contains only improvements for Docker image: Switch to PHP 8.3, standalone image package build, as well as fixes in the example compose files.

[!NOTE]
Note that the standalone version of the image is now generally available in the packages section here. Starting from this release, every new version will trigger both standard and standalone builds. For an example on how to use the standalone image, please refer to the related docker compose file

How to upgrade

Nothing if you're on v4.4.2+

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

davis - v4.4.3

Published by tchapi 5 months 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

davis - v4.4.2

Published by tchapi 7 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

davis - v4.4.1

Published by tchapi 9 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).

  2. 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

Thanks @MuratovAS for the challenge on auth mechanisms

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

davis - v4.4.0

Published by tchapi 9 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

davis - v4.3.0

Published by tchapi 11 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

davis - v4.2.1 (yanked)

Published by tchapi 11 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

davis - v4.2.0

Published by tchapi 11 months ago

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

davis - v4.1.0

Published by tchapi 12 months ago

What's Changed

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

davis - v4.0.0

Published by tchapi about 1 year ago

What's Changed

Warning

⚠️ This release drops support for PHP < 8.0 ⚠️

New Contributors

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

davis - v3.3.1

Published by tchapi about 1 year ago

What's Changed

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

davis - v3.3.0

Published by tchapi over 1 year ago

What's Changed

Note

This is 3.X branch's latest feature release. 4.X will drop support for PHP < 8.0.

New Contributors

SQLite

You can now use SQLite as a datastore. A sample docker-compose for SQLite is available in the repo to get you started. Please note that it is not extensively tested and that MariaDB is still the recommended database to run Davis

How to upgrade

Nothing to do, but make sure that you have upgraded to v3.1.0 before.

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

davis - v3.2.0

Published by tchapi over 1 year ago

What's Changed

  • Minor chores regarding CI and container build, not impacting the application itself
  • [Chore] Support PHP 8.2 in https://github.com/tchapi/davis/pull/80
    • Switch to PHP 8.2 for the container
  • Fix a bug about sharing when no other users exist in 5af380baf780f5596cfbc1aafbd53b9bb9f91126
  • Fix missing id fields and PG columns types in https://github.com/tchapi/davis/pull/86
  • Fix a misleading error status in 861d97b9439c18fcc3e2d65e37e9a34c0f5fdf40
  • Make 401 less verbose in 642bce7a07d6be3e6e500ad7c275bf48afd5881e
  • Update dependencies and dependency pinning for minimum versions
  • Update README

How to upgrade

Nothing to do, but make sure that you have upgraded to v3.1.0 before.

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

davis - v3.1.0

Published by tchapi almost 2 years ago

Warning
The previous 3.0.0 was yanked β€” you should switch to 3.1.0 (this release) directly

What's Changed

This change will also allow Davis to be used with a PostgreSQL database.

How to upgrade

Add the new env var

Specify DATABASE_DRIVER in your env file like so:

DATABASE_DRIVER=mysql

🚨 Breaking change β€” How to migrate your database

Warning
If you already use PostgreSQL (not supported), DO NOT FOLLOW THESE STEPS. See the "How to upgrade (PostgreSQL)" paragraph below for more information

This upgrade is a good time to enforce the use of migrations.

To do so, you will need to follow the necessary steps BEFORE UPGRADING:

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 your env var to use the serverVersion and charset

This is highly recommended as various database engines will yield different migration plans. You only need to change your DATABASE_URL env var to reflect the actual version of your server, and its charset:

For MariaDB, for instance:

DATABASE_URL=mysql://davis:password@mysql:3306/davis?charset=utf8mb4&serverVersion=mariadb-10.6.10

For MySQL:

DATABASE_URL=mysql://davis:password@mysql:3306/davis?charset=utf8mb4&serverVersion=5.7

Use the correct version of your database of course

2. Check the status of the migrations you have on your db

bin/console doctrine:migrations:status

It should yield a table, like so (some rows have been cut for readability):

+----------------------+----------------------+------------------------------------------------------------------------+
| Versions             | Previous             | DoctrineMigrations\Version20210928132307                               |
|                      | Current              | DoctrineMigrations\Version20221106220411                               |
|                      | Next                 | DoctrineMigrations\Version20221106220412                               |
|                      | Latest               | DoctrineMigrations\Version20221106220412                               |
|----------------------------------------------------------------------------------------------------------------------|
| Migrations           | Executed             | 7                                                                      |
|                      | Executed Unavailable | 0                                                                      |
|                      | Available            | 8                                                                      |
|                      | New                  | 1                                                                      |
+----------------------+----------------------+------------------------------------------------------------------------+

The important bit is if you have ever executed the migration, ie. if Migrations | Executed is not 0

3. Sync the migrations if necessary

a. You have executed at least 1 migration

You don't need to do much more, just skip to 4.

b. You have executed 0 migration

It means that you haven't run any migration before and that the schema was created ad-hoc. To fix this and make sure your db is in sync, we're going to do two steps:

  1. Force the update of the schema:
bin/console doctrine:schema:update --force
  1. Mark all migrations as passed:
bin/console doctrine:migrations:sync-metadata-storage
bin/console doctrine:migrations:version 'DoctrineMigrations\Version20191030113307' --add --no-interaction
bin/console doctrine:migrations:version 'DoctrineMigrations\Version20191113170650' --add --no-interaction
bin/console doctrine:migrations:version 'DoctrineMigrations\Version20191125093508' --add --no-interaction
bin/console doctrine:migrations:version 'DoctrineMigrations\Version20191202091507' --add --no-interaction
bin/console doctrine:migrations:version 'DoctrineMigrations\Version20191203111729' --add --no-interaction
bin/console doctrine:migrations:version 'DoctrineMigrations\Version20210928132307' --add --no-interaction
bin/console doctrine:migrations:version 'DoctrineMigrations\Version20221106220411' --add --no-interaction

Note
If you have an error like so The metadata storage is not initialized, please run the sync-metadata-storage command to fix this issue., this means that you have not updated your DATABASE_URL env var to use the server version as indicated in point 1.

4. 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.

[Unsupported] How to upgrade (PostgreSQL)

⚠️ if for some reason you are using a modified version of Davis with a PostgreSQL database, the latest migrations will likely not work as the data will not be converted when changing the column type.

In this case, you need to update manually the database structure and cast all necessary values accordingly (from bytea to varchar), and then mark the single PostgreSQL migration as run with:

bin/console doctrine:migrations:version 'DoctrineMigrations\Version20221106220412' --add

You can see all the columns that have been changed in the migrations\Version20221106220411.php file

Full Changelog: https://github.com/tchapi/davis/compare/v2.1.0...v3.1.0

davis - v3.0.0 (yanked)

Published by tchapi almost 2 years ago

Warning
THIS RELEASE IS YANKED

## What's Changed

  • We now use VARCHAR instead of VARBINARY for a bunch of columns
davis - v2.1.0

Published by tchapi almost 2 years ago

What's Changed

  • We now use Alpine Linux to create the Docker image

How to upgrade

If you don't use Docker or have not enabled WebDAV, there's nothing to do ✨

Otherwise, you need to be careful when updating:

On the previous Docker image, the www-data user had a uid of 33
Switching to Alpine, this same user now has a uid of 82 and the uid of 33 is assigned to the xfs user.

🚨 If you had a shared WebDAV volume used by the Davis container, make sure that the user set for the root WebDAV folder is correct, ie. you need this folder to be owned by www-data:www-data and not xfs:xfs (ie. 82:82 and not 33:33)

Full Changelog: https://github.com/tchapi/davis/compare/v2.0.2...v2.1.0

davis - v2.0.2

Published by tchapi over 2 years ago

This is just a minor release addressing an issue with the Docker container missing the freetype flag

Full Changelog: https://github.com/tchapi/davis/compare/v2.0.1...v2.0.2

davis - v2.0.1

Published by tchapi over 2 years ago

This is just a minor release containing a fix regarding the map marker image that was not searched in the right folder

Full Changelog: https://github.com/tchapi/davis/compare/v2.0.0...v2.0.1

Package Rankings
Top 6.75% on Proxy.golang.org
Badges
Extracted from project README
Build Status Publish Docker image Latest release Sponsor me
Related Projects
go-api-boilerplate

Go Server/API boilerplate using best practices DDD CQRS ES gRPC

14 Oct 2017 888
gripp-api-platform

Gripp Symfony

04 Jun 2019 7
angular-cli-skeleton

angular-cli skeleton to quickly start a new project with advanced features and best practices. Al...

14 Dec 2017 33
django-react-boilerplate

Django 5, React, Bootstrap 5 with Python 3 and webpack project boilerplate

08 Aug 2024 14
django-react-boilerplate

Django 5, React, Bootstrap 5 with Python 3 and webpack project boilerplate

19 Jul 2016 1,712