mirror of
https://github.com/Mailu/Mailu.git
synced 2024-12-14 10:53:30 +02:00
d1eab083f5
1831: Fix roundcube database env configuration r=mergify[bot] a=parisni ## What type of PR? bug-fix ## What does this PR do? Both roundcube and mailu admin website can be backed by postgres/mysql. Before this PR, the `DB_FLAVOR` is shared by both services. However, the other roundcube dedicated DB params are prefixed with `ROUNDCUBE_`. (eg: `ROUNDCUBE_DB_NAME`) There is no reason to share the DB_FLAVOR for both: This PR makes them be considered independently to make things clear and avoid bugs. Also, the roundcube_db_flavor and db_flavor are made separated in this PR. However for simplicity, the template generator bind them : roundcube_db_flavor = db_flavor. This makes the template generator UI more simple. I considered most of the time people want to have both roundcube and mailu share the same RDBMS. Also, AFAIK the internal postgresql service is deprecated and will be removed in 1.9. This is why this PR does not integrate roundcube in postgres when the internal DB is choosen: in case of internal postgres, the roundcube is backed with sqlite. Both documentation and setup website have been updated accordingly. ### Related issue(s) - Auto close an issue like: closes #1648 #1471 ## Prerequistes Before we can consider review and merge, please make sure the following list is done and checked. If an entry in not applicable, you can check it or remove it from the list. - [X] In case of feature or enhancement: documentation updated accordingly - [X] Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/guide.html#changelog) entry file. Co-authored-by: parisni <nicolas.paris@riseup.net> Co-authored-by: Nicolas Paris <nicolas.paris@riseup.net> |
||
|---|---|---|
| .. | ||
| docker-compose.yml | ||
| mailu.env | ||
| setup.html | ||