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

Enhancement: Allow local-only (on the filesystem) backup destination #121

Open
ernstae opened this issue May 23, 2018 · 1 comment
Open

Comments

@ernstae
Copy link
Contributor

ernstae commented May 23, 2018

I would like to use this software locally only, but am not able to deploy SSH keys for connecting back to localhost in a particular scenario.

Since it's already implemented to have a local copy saved, would it be possible to enable a local destination as a primary location (rather than s3 or ssh)?

I did start hacking on this, and hope to submit a PR, but wanted to open it up with the off-chance that a better coder might tackle it before I can.

@akuzminsky
Copy link
Member

The local copies right now are implemented in a modifier class. If the local copy is the final destination the LocalDestination should inherit from PeriodicCopy (currently the development is going in the develop branch.). The implementation should be straightforward.

Meanwhile, I'd suggest you to setup SshDestination to 127.0.0.1. You can check examples in the vagrant configs - for tests we do exactly that in vagrant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants