Add export/backup functionality to Command Line interface

  • Unknown's avatar
    melorama · Member ·

    I really wish Day One had a way to automate periodic local backups/exports of my Journal data. Because my journals contain memories that are literally priceless and irreplaceable, I’d like to be able to make sure that I always have local, scheduled, incremental backups of that data in an open format that can be parsed, in the event of server-side data loss, corruption or even a simple deletion mistake on my part.

    While you can export journal data via the File/Export menu, this is a manual process, which does not make for a robust personal backup plan. I also want to export my journal in all 3 available formats (JSON, PDF and Plain Text), just for redundancy’s sake, and this adds more friction to the process when manually exporting data via File/Export.

    Right now the CLI tool only has one command: “new”. I suggest adding another command, “export”, which would allow you to export all journal data, or only selected journals, and allow you to export them to different formats, so that backups can be scripted and scheduled.

  • staff-reid · Staff ·

    Hello @melorama,

    That’s a great suggestion and a feature I think a handful of others would use! I’ll get this submitted to the team for future consideration.

Reply to Add export/backup functionality to Command Line interface