Home / GitHub Page

Can I run a second instance of Joplin?


#1

I’m wondering, if there’s a way to start a second instance of Joplin.

I read about the --profile flag in the post Is there any way to use as a portable app?, but I have no idea to use that on macOS.

e.g. ./Joplin --help or ./Joplin -h only brings the current running Joplin version to the front.
Shouldn’t the above commands show a ilst of available command line options instead?

Can I use my running “production” Joplin app next to a second one, which I only start up for testing and/or developing?


#2

may be with something like this


#3

The --profile flag normally can be used in macOS too, though I wouldn’t know how to use this to make it portable.

At the moment, the app is limited to one running instance only - this was to avoid people accidentally running multiple instances in the background, all syncing with each others.

I wouldn’t be opposed to make this optional though as it would indeed be useful to run multiple portable versions of it - eg. one for work, one for personal notes, one to share projects, etc.


#4

Thanks. I did not mean how to invoke it, but rather how to make it spawn a second instance.
But apparently this is not supported.

Also, I was wondering why there’s no usage text for the command.


#5

I’d understand, if this limitation were enforced per profile. But if I had several profiles, it would be rather unlikely that this would happen. Unless the user explicitly sets the same settings, but there’s no help for stupidity.

I never really thought of using a different profile as portable. Portable only means that it can be run from a location without having to install it. This terminology usually only applies (in most cases) to Windows anyway.

But yeah, it would make sense during development to start the version one is working on with test notes.

Btw, any chance you could implement a --help flag that shows the list of command line options?


#6

Joplin already does that. When you run it with the run.sh script, it uses a separate dev profile.

Maybe the instance limit could be optional, or ‘off by default’ in the Portable app.
I really like the idea of one instance per profile, though. (A visual indication of which window belongs to which profile would be helpful (e.g. in the top bar) to avoid confusion. Or is that only me, who keeps hitting wrong windows when alt-tabbing between two dozen windows? :smiley: :sweat_smile:)


#7

It would indeed make sense, but I never did as I see these flags as non-official, more for advanced use.


#8

Awesome, good to know. Cheers.

I think I really need to understand what “portable app” means in the Joplin context. What is a Joplin portable app and what’s the difference to the standard app? The command line flags are available for both, so what has “portable” to do with the things I was asking?


#9

Thanks for the info. I always add some usage info, even if it’s just for expert/advanced usage. However, I do not show hidden flags by default. I only show them when a certain env var is set.


#10

I think I really need to understand what “portable app” means in the Joplin context. What is a Joplin portable app and what’s the difference to the standard app?

It means that all settings are saved in a directory (in this case “JoplinProfile/”) relative to the executable, so if you move it to somewhere else with a USB drive, the app will still work.

For the multiple instances, I agree it would make sense to scope them to the profile, so multiple apps could run, each with different profiles. It’s actually a better idea than making this an option as I’ve suggested.


#11

Do you have this in your backlog or shall I open a github issue?


#12

Yes feel free to open an issue to keep track of it, it’s not on the backlog at the moment.


#13

/ref https://github.com/laurent22/joplin/issues/591