Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make backup command independent of the Docker project name #130

Open
4 tasks
bschmalhofer opened this issue Jun 4, 2024 · 0 comments
Open
4 tasks

Make backup command independent of the Docker project name #130

bschmalhofer opened this issue Jun 4, 2024 · 0 comments
Milestone

Comments

@bschmalhofer
Copy link
Contributor

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:

  • 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.
@bschmalhofer bschmalhofer added this to the OTOBO 11.0 milestone Jun 4, 2024
@bschmalhofer 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant