|
|
|
@ -335,7 +335,7 @@ MYODOOSERVICENAME=odoo |
|
|
|
DBNAME="$MYODOOSERVICENAME" |
|
|
|
OUTPUTFILE=backup-odoo.zip |
|
|
|
cd /opt/apps/myc-deploy && |
|
|
|
compose save "$MYODOOSERVICENAME" "$DBNAME" "$OUTPUT_FILE" |
|
|
|
compose save "$MYODOOSERVICENAME" "$DBNAME" "$OUTPUTFILE" |
|
|
|
#+END_SRC |
|
|
|
|
|
|
|
The backup file should be in the same directory. |
|
|
|
@ -343,9 +343,12 @@ The backup file should be in the same directory. |
|
|
|
***** Restoring odoo account (filestore and database) |
|
|
|
|
|
|
|
There are still some quirks, so be sure: |
|
|
|
|
|
|
|
- to change your current directory to =/opt/apps/myc-deploy= |
|
|
|
and put your backup file in the same directory |
|
|
|
- your odoo instance should be already up. |
|
|
|
- an odoo base should not exist with the same name prior to restoring |
|
|
|
if it is the case, =ODOOBASE=odoo && pgm rm "$ODOOBASE" -f && rm -rf |
|
|
|
- to have =admin-password= defined in your =compose.yml=, in your |
|
|
|
=odoo= service's =options=. |
|
|
|
|
|
|
|
@ -355,7 +358,7 @@ odoo: |
|
|
|
admin-password: XXXXXX |
|
|
|
#+END_SRC |
|
|
|
|
|
|
|
*IMPORTANT* you might want to consider the usage of docker-cutoff if |
|
|
|
*IMPORTANT* you might want to consider the usage of =docker-cutoff= if |
|
|
|
you are restoring a production odoo onto a dev or staging odoo that you |
|
|
|
don't want to allow to go mess around with sending mails or fetching mails. |
|
|
|
|
|
|
|
|
