-
-
Notifications
You must be signed in to change notification settings - Fork 868
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roundcube user & DB missing in postgresql image #1471
Comments
I just upgraded from 1.7 to Master because I wanted to test Roundcube including CalDAV and Enigmail. I would be happy about a solution to this problem and I think Roundcube should use a dedicated database. |
I have solved the problem temporarily by adding the following line to the
The last commit was almost a month ago, and for a Docker based project, the last release was also a relatively long time ago. I also noticed that all Docker images are based on Apline 3.10, which makes tools like Rspamd very outdated. Version 1.9.4 for example was released in May 2019. I would like to support you in the development of Mailu, but I do not understand why even small pull requests like #1532 are not merged. |
Hi There, The To help with that, we are currently trying to find out which issues are actively keeping users from using In order for us to better assess this, it would be helpful if you could put a reaction on this post (use the 😃 icon to the top-right).
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
In order to get both roundcube and mailu on postgresql one have to add those configs to the env. This might be added to the documentation because currently roundcube crashes fallowing the postgres migration docs
|
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>
Fixed in #1831 |
#1268 added PostgreSQL support to roundcube. I generate a new config using Setup Utility and select the Mailu provided PostgreSQL image. This sets
DB_FLAVOR=postgresql
. In turn, Roundcube also goes in PostgreSQl mode and tries to connect to the database service with defaults:Mailu/webmails/roundcube/start.py
Lines 25 to 28 in 5798880
However, the PostgreSQL startup script does not create this user and DB:
Mailu/optional/postgresql/start.py
Lines 14 to 26 in 5798880
A choice has to be made:
pg_hba.conf
) to add this user and DB. Slight increase in complexity, while we are looking to retire the image.Opinions welcome. I'll implement, no worries.
PS: If we ship a stock image for PostgreSQL, by default it only creates 1 user and 1 database which names can be set by environment variables. If we need to use more users, some scripts would still be needed. https://github.com/docker-library/docs/blob/master/postgres/README.md#initialization-scripts
cc: @micw @kaiyou
The text was updated successfully, but these errors were encountered: