§ We are a lot in need of space on our laptops. So at some point it’s impossible to have the joplin’s database growing more and more on our local disks.
§ The path to notes and settings is shown here in Joplin’s options :
§ A solution would be to have the opportunity to select where we put our data from Joplin and to put it, for example, in an USB external hard drive or in an internal M.2 card, with enough space.
§ There’s two ways to organize that :
Joplin is installed on the local disk and data is on another (external or internal) disk.
Joplin is installed on another disk than the local one, with data too.
§ Under windows it’s already possible to have the second organization with the « portable » version of Joplin. I used it during many months. It’s slower than a local installation but it works.
On Windows, you may also use the Portable version. The portable application allows installing the software on a portable device such as a USB key. Simply copy the file JoplinPortable.exe in any directory on that USB key ; the application will then create a directory called "JoplinProfile" next to the executable file.
§ I tried many things with no success until now. With your help II would like to create here
a « howto » step by step (first : joplin local, data external) for everyone interested too...
Under KUBUNTU (Linux) if I try to start a appimage version of joplin located on the external hard drive, with double click I have this message: “your appimage is on a distant files sytem. For security reason, it will not be started”.
Maybe the solution is to change the file system on the drive, like they say here, but I can’t accept that… :
the filesystem was the issue as I can now successfully use the AppImage with localized data. Ventoy defaults to exFAT but supports ext4 if desired with the caveat that using Ventoy to boot isos will fail if you are trying to boot Windows or an OS that does not support ext4.
The ln command lets you create hard or soft links to files or directories. You can "map" ~/.config/joplin-desktop to a different folder on a different drive that actually contains your Joplin data. Joplin however thinks it is looking at ~/.config/joplin-desktop. I believe that you may need to use a soft link as hard links cannot cross file systems, which is what you would be doing if you wanted ~/.config/joplin-desktop on another drive.
I had a Linux Mint VM that had Joplin on it. Joplin had been used and ~/.config/joplin-desktop contained app data. I added a second drive (ext4) to the VM. The second drive was mounted at /media/vbox/Second_Drive/. After fully quitting Joplin I moved the entire ~/.config/joplin-desktop folder to /media/vbox/Second_Drive/. So the Joplin data was now stored at /media/vbox/Second_Drive/joplin-desktop and ~/.config did not contain a joplin-desktop folder. I then made a link back to ~/.config/ using the ln command.
This created a joplin-desktop link in ~/.config/.When Joplin was run it opened using the data on the other drive.
If ~/.config/joplin-desktop was ever deleted the data would still be there at /media/vbox/Second_Drive/ as just the link gets deleted. You can see the link and link properties in the screenshot.
This is the first time I have tried this and I only did it as I was interested to see if it would actually work. I do not intend to use this myself as disk space is not a problem for me. Also I would have to give it some serious testing before relying on it. I am not sure that it would be such a good idea to use a removable drive as I think things could go a bit wrong if you started Joplin when the drive was not attached. I stupidly killed my VM before realising that this was something that needed testing. You may want to try.
As I am far from an expert on this I am happy to be corrected by anyone else here on the forum.
Basically all I am saying that this is a way to do it. If you do try this you should do some serious testing first with non-critical data until you are happy that it works and is reliable
