-
Notifications
You must be signed in to change notification settings - Fork 292
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
Backup #12
Comments
Thanks for the suggestion! Hmm, where should the backup file be backed up, This seems to be a one-time thing per machine, and it should probably require user interaction (to merge information from old config files, etc) or at least alert the user. I'm not sure what's the best way of designing this feature. Maybe it's best to leave it up to the user, the way it is now? |
I think this is best left to the user. I'm going to go ahead and close it for now. Feel free to reopen it if you have any ideas. |
Voting for such a feature. |
Hmm, I guess we can reopen this issue. I still don't know what the best way of handling this is. Would every file go to the backup folder? What if there are name collisions? Should the backup folder mirror the directory hierarchy instead? I think there's some stuff to figure out before this could be implemented. And as of now, I still think it's best left to the user -- in the majority of cases that I can think of, this isn't something that needs to be handled multiple times, and so it's probably handled best on a case by case basis anyways. |
A KISS proposal
That only would add serenity, when eg in a hurry to deploy. |
Let's leave this as-is for now. |
It will be good if there is an option that will make dotbot backup the existing files and write over it.
The text was updated successfully, but these errors were encountered: