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

Migration via a cloudbox backup. #48

Closed
maximuskowalski opened this issue Dec 18, 2021 · 5 comments
Closed

Migration via a cloudbox backup. #48

maximuskowalski opened this issue Dec 18, 2021 · 5 comments

Comments

@maximuskowalski
Copy link
Contributor

Explore the possibility of a specific role or flag to indicate a Cloudbox backup is being used and avoid bringing in stale settings.

Ideas could be as simple as setting a shortcut on the restore drive, or dragging the wanted tarred app files into the saltbox default.

I imagine this being required only for those that are quite new to X box or do not understand the backup restore process.

I would consider priority low as it would be a one shot use.

Similarly might be to consider the PG restorers if structure is close enough and I think it is.

@owine
Copy link
Collaborator

owine commented Dec 18, 2021

Parse log_path in the backed up ansible.cfg to establish which flavor is being run.

@ben-ba
Copy link

ben-ba commented Dec 27, 2021

A migration path would be nice, to easy switching to Saltbox.

@saltydk
Copy link
Member

saltydk commented Jan 1, 2022

Parse log_path in the backed up ansible.cfg to establish which flavor is being run.

I don't see the point as there is no difference if you're restoring from Cloudbox or Saltbox currently. Ultimately all this boils down to changing a path if you want to have new backups go to a different folder than the Cloudbox one.

@saltydk
Copy link
Member

saltydk commented Jan 1, 2022

Only the restore service brings over the config files so I am not really following what it is you ultimately want here. Please be specific and try not to ask for vague things.

@saltydk
Copy link
Member

saltydk commented Apr 5, 2022

Closing this as I believe this is solved by our docs at this point.

@saltydk saltydk closed this as completed Apr 5, 2022
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

4 participants