* Added entrypoint hooks for your own custom scripts
Signed-off-by: Dennis Vestergaard Værum <github@varum.dk>
* Small changes:
- Only execute shell-scripts (mening files ending with .sh)
- Sort the files before executing them, had forgotten 😅
- Added a message when a hook script finish
- Added prefix arror to message to show the are related
Signed-off-by: Dennis Vestergaard Værum <github@varum.dk>
* Show in the search msg that it only searches for '*.sh' files
Signed-off-by: Dennis Vestergaard Værum <github@varum.dk>
* Fixed spelling mistake
Co-authored-by: J0WI <J0WI@users.noreply.github.com>
Signed-off-by: Dennis Værum <6872940+dvaerum@users.noreply.github.com>
* Updated the `README.md` file
Signed-off-by: Dennis Vestergaard Værum <github@varum.dk>
* change from using find to using a for-loop to located the `.sh` files
Signed-off-by: Dennis Vestergaard Værum <github@varum.dk>
* Fix bug - that would make docker-entrypoint.sh failed, hook folders was empty
Signed-off-by: Dennis Vestergaard Værum <github@varum.dk>
---------
Signed-off-by: Dennis Vestergaard Værum <github@varum.dk>
Signed-off-by: Dennis Værum <6872940+dvaerum@users.noreply.github.com>
Co-authored-by: J0WI <J0WI@users.noreply.github.com>
* README: update to reflect support of these images vs enterprise and AIO
Signed-off-by: Simon L <szaimen@e.mail.de>
* address review by J0WI
Signed-off-by: Simon L <szaimen@e.mail.de>
---------
Signed-off-by: Simon L <szaimen@e.mail.de>
* 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>
Updated the wording of the comments for one of the docker-compose examples to more correct english usage.
Signed-off-by: Charlie MacFarlane Brodie <mail@charliebrodie.com>
* Added fetching autoconfig data from Docker secrets
Signed-off-by: Simon Tushev <tushev@users.noreply.github.com>
* Docker secrets now have priority over ENV variables; improved README.md
Signed-off-by: Simon Tushev <tushev@users.noreply.github.com>
The environment variable for MYSQL_DATABASE was named MYSQL_DB in chapter "Docker Secrets".
The typo probably happened because of inconsistent naming of MYSQL_DATABSE vs POSTGRES_DB.
Replaced incorrect environment variable name `OBJECTSTORE_SWIFT_SERVICE_REGION` by `OBJECTSTORE_SWIFT_REGION`.
As visible in f1ca6dbfab/19.0/fpm/config/swift.config.php (L25), configu read `OBJECTSTORE_SWIFT_REGION` instead of `OBJECTSTORE_SWIFT_SERVICE_REGION`.
* Environment variables in docker-compose section
Docker-compose file in the example was missing database configuration environment variables of the app container, making the stack to use SQLite by default instead of the DB container.
Didn't add `NEXTCLOUD_ADMIN_*` variables since this addresses the DB being configured with SQLite. This still works setting up admin credentials on first NC run.
Signed-off-by: tetebueno <9064236+tetebueno@users.noreply.github.com>
* Fixing FPM version too.
Signed-off-by: tetebueno <9064236+tetebueno@users.noreply.github.com>
