Edit: Disregard this answer — the --profile
flag is intended only for debugging (for example, it's used for automated testing in GitHub CI).
According to @laurent, improper usage of --profile
flag can lead to data loss (particularly if used to force different versions of the app (e.g. desktop and CLI) to use the same profile).
Original
Its contents should look similar to this:
{
"version": 2,
"currentProfileId": "48bmx57y",
"profiles": [
{
"name": "Default",
"id": "default"
},
{
"name": "Profile 2",
"id": "48bmx57y"
},
{
"name": "Profile 3",
"id": "zd48x96h"
},
{
"name": "Profile 4",
"id": "g2sj7zuy"
}
]
}
Observe that each profile has an id
. There should be corresponding profile-id
folders for each profile in ~/.config/joplin-desktop/
. For example, Profile 4
has a profile-g2sj7zuy
folder.
As such, for me,
joplin-desktop --profile ~/.config/joplindev-desktop/profile-g2sj7zuy
would launch Joplin with Profile 4
.
Note that it doesn't seem possible to run both at once, because of Joplin's single instance check.