Hi @laurent,
due to the more and more plugins and also settings in the plugins, maybe a function or menue to export / import the settings as JSON would be great.
Passwords, tokens, ... should not be exported or only as empty string.
What do you think?
Regards
Alex
Yes that makes sense. Ideally we should make this change that's been discussed before of putting all user settings in an external JSON file, so that it can be backed up and restored more easily. I'll probably look at this rather than have a function to import/export from the database.
Yes, that is indeed a very important feature. I would need it right now, but well, nothing I can do about that.
I'd love to be able to export the list of plugins that I use so that I can import on another system. Right now I use Joplin on 2x Mac, 1x Linux and 1x Windows machines (!!) and there's no easy way to get the same plugins on all of them. Also, since I cannot open the preferences and also have a note open to edit (that I know about?), I cannot make a list in a note while looking at the prefs - unless I do that in another editor!
Install plugins on one machine and then copy ~/.config/joplin-desktop/plugins (or the equivalent path on Mac/Windows) to other machines. This will sync plugins but not plugin settings.
Ah, that's helpful - thank you!
For what its worth one of the ideas for GSoC is to implement a settings sync which should include plugins and plugin settings.
Yes, migrating without setting and plugins sync is painful but not critical.
Also custom css should be included.
@laurent I would like to bring up the subject again. To backup the increasing number of plugins and their settings.
Many of the settings are now in a json file, and normally what's left in the database is more like application state that shouldn't be shared. Or did you notice some settings that are missing from the json file?
It's possible to store plugin settings in the JSON file (using SettingStorage.File, example).
It's opt-in, however, so I'm not sure how many plugins do this.
On a quick check, only one plugin and thats yours.
How can this be streamlined to other existing plugins?
How can this feature be made more visible to plugin developers?
