Update Docker documentation with backup instructions#267
Conversation
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 |
|
|
||
| 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. |
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
There was a problem hiding this comment.
@thimios so is there an adjusted sentence to replace this with, or should this PR be closed?
There was a problem hiding this comment.
I propose that instead of:
It is also very important you perform regular backups of your ArchivesSpace MySQL database. Follow the steps under the Backup and recovery section if you need more instructions on how create backups of your MySQL database.
We write:
The docker configuration package already includes a confIt is also very important you perform regular backups of your ArchivesSpace MySQL database. Follow the steps under the Backup and recovery section if you need more instructions on how create backups of your MySQL database.igurable database backup mechanism for MySQL. Read more about it here
3 participants
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.