Do not use the mailcow database for all third party applications
fabreg opened this issue · comments
Summary
Many third party application like gitea and others requires to setup a database.
Actually all those third party applications uses "mailcow" as database: it should be nice if every third party application uses its own database without adding tables to the original one "mailcow"
Motivation
Motivation is pretty simple: if you have a problem on third party application you are not able to understand which tables are used because they are drown inside mailcow database.
Additional context
No response
Actually all those third party applications uses "mailcow" as database:
Where did you get this information? I could not find it in the docs 🫣..
There's no information about that in the docs, but you can easily install gitea for example and verify it.
I will move this issue to the https://github.com/mailcow/mailcow-dockerized-docs repo.
You can create a PR if you want.
Anyway:
Since mailcow/mailcow-dockerized@9c55d46 the nextcloud helper-script will use a dedicated database for nextcloud
For the other stuff like Gitea or Roundcube it's indeed using the mailcow database, seems like Gitea would be easy to change the docs, for roundcube not since it uses getenv so need to change a bit more.
He`s right though and i have the same opinion on that.
Heck the nextcloud bundled installer was doing the same before i changed it a few releases prior.
So yeah, good advice will be noted down.
I will move this issue to the https://github.com/mailcow/mailcow-dockerized-docs repo. You can create a PR if you want.
Anyway: Since mailcow/mailcow-dockerized@9c55d46 the nextcloud helper-script will use a dedicated database for nextcloud
For the other stuff like Gitea or Roundcube it's indeed using the mailcow database, seems like Gitea would be easy to change the docs, for roundcube not since it uses
getenvso need to change a bit more.
I will try to do something for gitea at least, then I will rise a PR.
Please have a look at #528
Thanks!