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

knife-tarsnap thoughts #11

Open
ghost opened this issue Aug 14, 2013 · 0 comments
Open

knife-tarsnap thoughts #11

ghost opened this issue Aug 14, 2013 · 0 comments

Comments

@ghost
Copy link

ghost commented Aug 14, 2013

I attempted to add some additional functionality to the knife-tarsnap command a few months back, and ran into a issue. Some tarsnap commands require access to your tarsnap cache directory.

This leaves two solutions.

  1. Allow users to specify a tarsnap cache directory to be used.
  2. Change it so tarsnap is run over ssh instead.

The first option would be much quicker to implement, but would make at least the first run much slower.

Option two would be my preferred method for a couple reasons. You don't have to worry about the cache dir, and it doesn't require the user to have tarsnap on their dev machine.

If you don't mind deciding what way you would prefer to go, I would be happy to do the work.

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

0 participants