Provide docker-compose setup for production (#1)

* chore: Add docker compose file for production

* chore: Ignoring unnecessary files after initial docker-compose setup for production environment

* chore: Switch to mariadb

* chore: Enable ssl connection for mariadb

* chore: Add ETHERPAD_PLUGINS and more env vars from the kitsteam

* chore: Add config for etherpad plugin ep_delete_after_delay

* chore: Finalize brnach

* chore: Fix wrong chartset passed to etherpad and ueberdb2 config

* docs: Add kits-specific documentation for database migration

Co-authored-by: Gerardo Navarro <gerardo@b310.de>
This commit is contained in:
Gerardo Navarro Suarez 2022-09-20 15:39:42 +02:00 committed by Gerardo Navarro
parent 80c9932008
commit 1714ff6116
6 changed files with 147 additions and 2 deletions

15
README-KITS.md Normal file
View file

@ -0,0 +1,15 @@
## Etherpad Lite for KITS
## Maintenance
### Restore MariaDB backup
```bash
docker compose -f docker-compose-prod.yml -f docker-compose-prod.override.yml --env-file .env.prod exec -T mariadb_prod mysql -u prod_database_user --password=prod_database_user_password -D prod_database_name < path_mysql_dump.sql
```
If you want to create a dump in a new database then you should execute the following command beforehand:
```bash
docker compose -f docker-compose-prod.yml -f docker-compose-prod.override.yml --env-file .env.prod exec -T mariadb_prod mysql -u root -p -e "CREATE DATABASE IF NOT EXISTS prod_database_name; GRANT ALL PRIVILEGES ON prod_database_name.* TO prod_database_user@localhost"
```