Jrnl: Enhancement Request: Keep Backup Journal File

[makais]

Request to add an option to create a backup of the journal file upon saving, such that a specified number of previous versions are retained. In the case of a corrupted file or crash, this would avoid catastrophic data loss by reducing it to only the most recent change.

[eshrh]

Isn't it easier to just use a DayOne journal to constantly back up the file?

[sorsasampo]

It does not make sense to reimplement a VCS (Version Control System).

Would be better if jrnl could (configurably) notice that the journal file has been added to git, and automatically commit any changes to it.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[wren]

I like the git idea, since it seems much easier to implement. But even that--and any other versioning--could get really dicey with encrypted journals, though, since it can't properly version them. I think saving your journal in a folder that is backed up by a proper backup system is best.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.