You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This command assumes that the Docker project name is otobo and used that name for the options --volume and --network. This works fine in most installations, but causes confusing errors when a different name is declared in ,env.
TODO:
document that the backup script must be called in the docker-compose directory on the Docker host
extract the project name from .env
use the correct name in the backup command
as a bonus: use the declared IMAGE in the command or use docker compose exec.
The text was updated successfully, but these errors were encountered:
bschmalhofer
changed the title
Make backup command indepent of the Docker project name
Make backup command independent of the Docker project name
Jun 4, 2024
In https://doc.otobo.org/manual/installation/11.0/en/content/backup-restore-docker.html there is the command
docker_admin>docker run -it --rm --volume otobo_opt_otobo:/opt/otobo --volume otobo_backup:/otobo_backup --network otobo_default rotheross/otobo:latest-11_0 scripts/backup.pl --extra-dump-options="--single-transaction" -d /otobo_backup
This command assumes that the Docker project name is
otobo
and used that name for the options--volume
and--network
. This works fine in most installations, but causes confusing errors when a different name is declared in ,env.TODO:
docker compose exec
.The text was updated successfully, but these errors were encountered: