Update Docker documentation with backup instructions #267
+4
−0
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
Deploying archivesspace-tech-docs with
|
| Latest commit: |
5a3b972
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://519e9e07.archivesspace-tech-docs.pages.dev |
| Branch Preview URL: | https://note-on-initalize.archivesspace-tech-docs.pages.dev |
thimios
previously requested changes
Jan 6, 2026
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.
brianzelip
force-pushed
the
note-on-initalize
branch
from
d4069dc to
5a3b972
Compare
brianzelip
approved these changes
Feb 9, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.