Update Docker documentation with backup instructions #267
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added notes about removing the .sql file and performing regular backups. In theory not removing that could result in it replacing the new database. I know the backup thing is a repeat but I don't think we can repeat this too many times.
Deploying archivesspace-tech-docs with
|
| Latest commit: |
d4069dc
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://46a1f1f7.archivesspace-tech-docs.pages.dev |
| Branch Preview URL: | https://note-on-initalize.archivesspace-tech-docs.pages.dev |
thimios
requested changes
Jan 6, 2026
|
|
||
| After the initial run you will want to remove that `.sql` file from the `sql` directory of your unzipped Docker configuration package. | ||
|
|
||
| It is also very important you perform regular backups of your ArchivesSpace MySQL database. Follow the steps under the [Backup and recovery](/administration/backup/) section if you need more instructions on how create backups of your MySQL database. |
Contributor
There was a problem hiding this comment.
I think this will be confusing, as the docker configuration package already includes a mechanism for automatic mysql backups: https://github.com/archivesspace/archivesspace/blob/master/docker-compose-prod.yml#L37 that is documented here: https://docs.archivesspace.org/administration/backup/#backups-when-using-the-docker-configuration-package
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added notes about removing the .sql file and performing regular backups. In theory not removing that could result in it replacing the new database.
I know the backup thing is a repeat but I don't think we can repeat this too many times.