The cron container requires the files created by the app container, to
start its cron tasks. There is a potential race condition here, where
cron starts to run before the app container is even up, before the app
container has populated `/var/www/html`. This is undesired and easily
solved by making sure cron depends on the app container.
Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
There doesn't seem to be a need to prefer building custom containers,
just to add a config file, a need that is easily solved with compose
configs. Configs are still managed through git, just no new container
needs to be built, slightly simplifying things.
Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
* Enable MariaDB binary log
This resolves a warning in the database server log:
[Warning] You need to use --log-bin to make --binlog-format work.
Pros:
* support for point-in-time recovery
* necessary for replication
Cons:
* slows down database operations ("slightly", per the manual)
* takes up disk space (mitigated by `--expire-logs-days=2`)
See also:
* <https://mariadb.com/kb/en/binary-log/>
* <https://mariadb.com/kb/en/full-list-of-mariadb-options-system-and-status-variables/>
Alternatives:
1. Do not add `--log-bin`. Remove `--binlog-format` instead. This causes the least amount of change for existing installations.
Signed-off-by: Adam Monsen <haircut@gmail.com>
* remove --expire-logs-days=2 mariadb flag
This better aligns with recommendations in the Nextcloud documentation.
Also: the flag isn't necessary. There are already set times for cleanup: The MySQL and MariaDB documentation both state that binary logs will be purged on startup and flush/rotation.
Signed-off-by: Adam Monsen <haircut@gmail.com>
---------
Signed-off-by: Adam Monsen <haircut@gmail.com>
* enable mariadb auto upgrade
This fixes after-upgrade issues, for example:
[ERROR] Incorrect definition of table mysql.event: expected column 'definer' at position 3 to have type varchar(, found type char(141).
The upgrade only happens when necessary.
I also disabled the system database backup because I assume users create
and test their own backups.
Signed-off-by: Adam Monsen <haircut@gmail.com>
* use 1s instead of "yesplease"
Any nonzero value is valid for these environment variables.
Signed-off-by: Adam Monsen <haircut@gmail.com>
Signed-off-by: Adam Monsen <haircut@gmail.com>
From https://www.nginx.com/blog/tuning-nginx/:
In most cases, running one worker process per CPU core works well,
and we recommend setting this directive to auto to achieve that.
There are times when you may want to increase this number,
such as when the worker processes have to do a lot of disk I/O.
This ensures that the remaining NGinx config examples are updated to handle WOFF 2 font files.
Closes#674.
Signed-off-by: Guy Elsmore-Paddock <guy@inveniem.com>
