Update backup.md
Added manual backup method first draft
This commit is contained in:
parent
c1605454dd
commit
0ae1ecd867
@ -25,4 +25,21 @@ They can be found in the mediafiles mounted directory (depending on your install
|
||||
|
||||
To create a backup of those files simply copy them elsewhere. Do it the other way around for restoring.
|
||||
|
||||
The filenames consist of `<random uuid4>_<recipe_id>`. In case you screw up really badly this can help restore data.
|
||||
The filenames consist of `<random uuid4>_<recipe_id>`. In case you screw up really badly this can help restore data.
|
||||
|
||||
## Manual backup from docker build
|
||||
The standard docker build of tandoor uses postgresql as the back end database. This can be backed up using a function called "dumpall". This effectively generates a list of commands for a postgresql server to use to rebuild your database. You will also need to back up the media files separately.
|
||||
|
||||
Making a full copy of the docker directory can work as a back up, but only if you know you will be using the same hardware, os, and postgresql version upon restore. If not, then the different version of postgresql won't be compatible with the existing tables.
|
||||
|
||||
To back up:
|
||||
```
|
||||
Sudo docker exec -t db_recipes -c -U djangouser
|
||||
```
|
||||
|
||||
To restore:
|
||||
```
|
||||
Cat dump.sql | docker exec -i psql postgres -U djangouser
|
||||
```
|
||||
This connects to the postgres table instead of the actual dgangodb table, as the import function needs to delete the table, which can't be dropped off you're connected to it.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user