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
Is your feature request related to a problem? Please describe.
Since there can occasionally be irrecoverable errors during early development, it would be nice to have a simple backup capability. I know fancy ones are planned, but "perfect enemy of good" etc :)
Describe the solution you'd like
What I do manually is go into AppData Roaming tech.trobonox.kanri and copy .kanri.dat to an external backup folder, and give it a name like .kanri-241105.dat
If this were done by the app when closed, or every day, that would be nice.
Describe alternatives you've considered
Here I'm thinking of the SIMPLEST possible backup process. It doesnt have to be integrated into the UI etc, it just has to be some file that you know is somewhere and you go find it if some data is lost. In fact it shouldnt be fancy, that would be a timesink on your part, and you can worry about fancy backups in the future. Just my 2p.
The text was updated successfully, but these errors were encountered:
The automatic copy of the file is exactly what I had in mind, I just didn't have the time to implement it yet (lot of personal stuff going on and generally need to iron out a lot of smaller things).
Thanks for reminding me of this.
Is your feature request related to a problem? Please describe.
Since there can occasionally be irrecoverable errors during early development, it would be nice to have a simple backup capability. I know fancy ones are planned, but "perfect enemy of good" etc :)
Describe the solution you'd like
What I do manually is go into AppData Roaming tech.trobonox.kanri and copy .kanri.dat to an external backup folder, and give it a name like .kanri-241105.dat
If this were done by the app when closed, or every day, that would be nice.
Describe alternatives you've considered
Here I'm thinking of the SIMPLEST possible backup process. It doesnt have to be integrated into the UI etc, it just has to be some file that you know is somewhere and you go find it if some data is lost. In fact it shouldnt be fancy, that would be a timesink on your part, and you can worry about fancy backups in the future. Just my 2p.
The text was updated successfully, but these errors were encountered: