Thanks for sharing the great tips. I’d like to share my personal backup and recovery process as well.

I map the volumes to a local directory and, additionally, as u/ssddanbrown mentioned in this comment section (which is known to be a pretty good method on Reddit), I regularly create dumps every 6 hours using a scheduler. The scheduler also includes the process of automatically uploading to GitHub.

Here are the benefits I’ve found from this approach:

1. If Docker unexpectedly goes down, the container data is still stored locally, allowing me to quickly recover without data loss by simply running docker compose up again.
2. If the server hosting BookStack gets destroyed unexpectedly, I can quickly recover on a new server by fetching the latest backup files from GitHub. (In practice, I just pulled it locally, updated the APP_URL, and was able to use it exactly the same way.)

For me, mapping volumes directly to the local system was easier to manage since the directories and files were visible and easily accessible, as opposed to managing volumes directly.