Open GoogleCodeExporter opened 9 years ago
Good idea.
Original comment by matt.rasmus@gmail.com
on 2 Mar 2011 at 11:13
The best solution to backup scheduling would be to accept a command line option
like `--export /path/to/file`. Then people could use their system scheduler
(like cron or whatever windows uses) to dump backups.
This has benefits:
* Gives you less code to maintain
* Lets people make their backup schedule+logic as simple or as complex as they
want without involving you. If you implement this in the program itself,
you'll get a bunch more bugs about people who want to do complicated things
like exporting every other day or only if the backup file isn't newer or to
keep the latest 5 backups and then start deleting them, etc. That's all logic
they could write themselves in a script.
Original comment by clouserw
on 6 Jun 2011 at 3:13
Well, Keepnote only does "tar zcf backup-DATE path/to/file" so one could just
do that in their backup scripts.
Also many backup systems do incremental backups and keepnote's file structure
should play nicely with them already.
I probably would not implement this automatic backup in keepnote. Existing
backup software is probably the safer and more flexible way to go.
Original comment by matt.rasmus@gmail.com
on 13 Jun 2011 at 1:44
Original issue reported on code.google.com by
sprocke...@gmail.com
on 2 Mar 2011 at 5:53