Include docker-compose steps in hosting for localized database backups

[aaronkanzer]

Provides docker-compose steps that allow an end user to easily access and run commands for data integrity and reliability against a local fossil-db and postgres instances

Cc @kabilar

URL of deployed dev instance (used for testing):

N/A

Steps to test:

• Create a deployment of WebKNOSSOS via instructions on https://docs.webknossos.org/webknossos/installation.html
• Once all containers are healthly on your local EC2, run docker-compose run --rm fossil-db-backup
• Confirm backup is present in /persistent/fossildb/backup/private on EC2 instance
• Run docker-compose run --rm fossil-db-restore to observe successful restoration
  (additionally, you can destroy the local fossildb instance and see if you can re-populate via restore)

TODOs:

• Include similar docker-compose scripts for pg_dump equivalent

Issues:

• fixes #

---

(Please delete unneeded items, merge only when none are left open)

• Updated changelog
• Updated migration guide if applicable
• Updated documentation if applicable
• Adapted wk-libs python client if relevant API parts change
• Removed dev-only changes like prints and application.conf edits
• Considered common edge cases
• Needs datastore update after deployment

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ aaronkanzer
❌ Aaron Kanzer

---

Aaron Kanzer seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[normanrz]

Thanks for your PR. I agree that it would be useful to include the backup commands in the docker-compose.yaml. I wonder if we should add a backup.sh to also zip up the fossildb backup with a timestamped filename?

I don't think the explicit networks are required and would prefer to keep them out.

In order to merge PRs from contributors, we need the CLA check to pass. For that all commits need to be authored with matching email info. Sorry for the inconvenience.

[normanrz]

Suggested change

container_name: webknossos-fossildb-1

[normanrz]

Suggested change

	image: scalableminds/fossildb-client:master
	image: scalableminds/fossildb-client:master__489

[normanrz]

Suggested change

	command: ["webknossos-fossildb-1", "backup"]
	command: ["fossildb", "backup"]

[normanrz]

I don't think an explicit network is required. We don't have that in our docker compose-based deployments.

Suggested change

	networks:
	- webknossos_default

[normanrz]

Suggested change

	networks:
	- webknossos_default

[normanrz]

Suggested change

	# Example command: docker-compose run --rm fossil-db-restore
	fossil-db-restore:
	# Example command: docker-compose run --rm fossildb-restore
	fossildb-restore:

[normanrz]

Suggested change

	# Example command: docker-compose run --rm fossil-db-backup
	fossil-db-backup:
	# Example command: docker-compose run --rm fossildb-backup
	fossildb-backup:

[normanrz]

Suggested change

	- postgres
	postgres:
	condition: service_healthy

[normanrz]

Suggested change

	image: postgres
	image: postgres:15-bullseye

[normanrz]

Suggested change

	command: [ "/bin/bash", "-c", "PGPASSWORD=postgres pg_dump -Fc -h postgres -U postgres webknossos | gzip > /backups/backup_$(date +%Y-%m-%d_%H-%M).sql.gz" ]
	command: [ "/bin/bash", "-c", "pg_dump -Fc -h postgres -U postgres webknossos | gzip > /backups/backup_$(date +%Y-%m-%d_%H-%M).sql.gz" ]
	environment:
	PGPASSWORD: postgres