coop-cloud/backup-bot-two
coop-cloud/backup-bot-two
6
0
Fork 4
Code Issues 9 Pull Requests Packages Projects Releases Wiki Activity

How can abra use restore_path? #62

New Issue
Closed
opened 2024-10-28 16:27:01 +00:00 by decentral1se · 2 comments
decentral1se commented 2024-10-28 16:27:01 +00:00
Owner
Copy Link

It follows a quite different logic, as these parameter get invalid --volumes, --container, --no-commands and it requires new PATHS argument. Seems a bit overloaded for one command. This can confuse people.

4b4371ed3f

> It follows a quite different logic, as these parameter get invalid --volumes, --container, --no-commands and it requires new PATHS argument. Seems a bit overloaded for one command. This can confuse people. https://git.coopcloud.tech/coop-cloud/backup-bot-two/commit/4b4371ed3f61dee80acd0bdd09132e44ad62dbdb
moritz commented 2024-10-28 16:38:22 +00:00
Owner
Copy Link

abra could detect if the app is deployed and then executes backup restore-paths instead of backup restore.
For this abra would need to extract from the given --container the connected volumes and from these volumes or the volumes given by --volumes the paths can be generated, i.e. /var/lib/docker/<service_name>_<volume_name>.
Than abra app restore could run INCLUDE_PATH=path1,path2 SERVICE=<service_name> backup restore-paths if it detects the app as undeployed.

`abra` could detect if the app is deployed and then executes `backup restore-paths` instead of `backup restore`. For this `abra` would need to extract from the given `--container` the connected `volumes` and from these volumes or the volumes given by `--volumes` the paths can be generated, i.e. `/var/lib/docker/<service_name>_<volume_name>`. Than `abra app restore` could run `INCLUDE_PATH=path1,path2 SERVICE=<service_name> backup restore-paths` if it detects the app as undeployed.
decentral1se commented 2024-10-29 15:31:13 +00:00
Author
Owner
Copy Link

Aiming for abra app backup restore and then dealing with deployed/undeployed logic internally! We've weighed up some UI/UX concerns and this seems like the best way forward for now.

Aiming for `abra app backup restore` and then dealing with deployed/undeployed logic internally! We've weighed up some UI/UX concerns and this seems like the best way forward for now.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant aadil abra-bot ammaratef45 Apfelwurm appletalk arjan basebuilder Brooke carla cas codegod100 coopcloud decentral1se fauno flancian Frando iexos javielico kawaiipunk knoflook lambdabundesverband mac-chaffee marlon mayel mirsal moritz nicksellen notplants p4u1 pau renovate-bot rix sef simon stevensting tobias trav val virtualboys wolcen wykwit xynosis yksflip
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/backup-bot-two#62
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?