Backup should not create directory in home

[pihentagy]

Nice to have a backup, but could you use one of the standard ~/.config or ~/.local/share directories and not create a directory under ~?

[JackGruber]

I assume you mean for the default installed plugin in Joplin.
The plugin here does not set a config for a backup directory, this is done by the Joplin team in the Joplin app.

[pihentagy]

Oh, I see. So I should report it about joplin itself, right?

[JackGruber]

I think they have chosen this path with intent, but please ask in the forum (mention that it is the default plugin) and post the link here if you like. I would also leave the issue open until this has been clarified.

[personalizedrefrigerator]

Nice to have a backup, but could you use one of the standard ~/.config or ~/.local/share directories and not create a directory under ~?

The default backup directory was chosen to be easy to find across platforms (e.g. so that users know that a potentially large backup is being created). At present, it's possible to change the backup location in Joplin's settings.

• ~/.config: I think the backup location used to default to ~/.config/joplin-desktop/JoplinBackup, but that was decided against because ~/.config/joplin-desktop/ is might be deleted when uninstalling Joplin.
• ~/.local/share: This could make sense.
  • Benefits:
    • Less cluttered home directory.
    • ...
  • Potential drawbacks:
    • The backup directory could be more difficult to discover.
    • Would this be Linux specific? If so, it could be more difficult to document the backup location — separate documentation would be needed for Linux, Windows, and MacOS.

Thank you for the feedback!

[pihentagy]

Well, that is indeed platform specific.

But that Browse... button next to the Backup path could show you the current backup path (It does not do that for me)