You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Allow users to specify a tarsnap cache directory to be used.
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: