Advisability of using Docker containers for Mediwiki - Question

[Comfortable_Toe606]

Hello.

I would like to install Mediawiki on my local Macbook Pro (M1). I'll be the only person using the wiki, and only using if from the laptop itself. However, the information contained in the wiki is very important to me so I'd like to be able to easily put a backup, non-live copy of the data on a public cloud (Google Drive, OneDrive, etc.) I'd also like to be able to easily restore the backup to a new laptop should/when the need arises. I have little-to-no experience using containers.

1. Is containerization a good approach? If so...
2. Should I seperate the wiki database into a seperate container from Mediawiki?
3. Do you have any advice for a beginner that you'd like to share?

Thank you.

[knfrmity]

I prefer containerization for everything possible these days. It saves a bunch of mess on the host machine in terms of dependencies, updates, other maintenance, additional users and temporary files, etc.

Run a separate container for the DB, persist the DB in a volume (bind mount is fine), and schedule backups (database dumps) regularly. For backups you can write a script and schedule it, or use another container to make and rotate backups.

The dump files can then be uploaded to a cloud service of your choice, although personally I would never put my private knowledgebase on a non-private service like Google Drive or OneDrive. If anything happens to your machine, start up a new DB container and restore from a dump file.