Joplin notes web client?

Features
1

Hello,
I'm really satisfied with my setup: raspberry Pi4 + joplin server.
Joplin server sync is really fast (10GB+ notes) compared to my previous setup with an old qnap + webdav.
And now I can publish single notes and get an external url!
I fear to ask here since there have been lots of discussions about it, but I've never got a clear reply to this question: is in the plan/roadmap to create a web client so that ALL notes/notebooks are automatically published and you can access them everywhere with an internet connection?
TIA
tony

2

Web client:

If you mean that all notes should be public by default, then I dunno.

3

Thanks for the link.
But it's not practical to me. I should resync all my notes on every browser I need to use.
Having installed Joplin Server I would imagine to see all notes published and be able to browse them using any browser (after loggin in, of course).
Tony

4

In 3.7 there's a feature to publish a while notebook to the internet. Is that what you mean?

5

@laurent I'm interested to know if I can log into my Joplin server (self-hosted on Cloudron) and be able to access (create/edit/read/write) my notes in the web browser without having to use the desktop/mobile clients. Is this currently possible or on the roadmap? In essence, an online Joplin editor. Thanks.

6

Having installed Joplin server, I would like to browse/edit notes online like evernote. Just like:

  1. Login
  2. Browse
  3. Edit
  4. Logout

A sort of Web client, but without the need to sync all notes everytime, since the notes are already on the server.
Tony

7

I‘ve developed such a solution, called Jarly. If anyone is interested in, I can share the docker image after my vacations.

Max

8

That would be awesome @piepmax!
I tried joplock, but that seems a bit shaky. Curious about your implementation

9

This is how I access my Joplin data securely from anywhere.

A self-hosted Joplin Desktop container accessible via VNC over LAN or VPN.

What it is

Joplin Desktop (the full Electron app) running inside a Docker container on Ubuntu 24.04 with a minimal Openbox window manager, exposed via x11vnc. The container syncs notes to S3, making it an always-on secondary Joplin workstation accessible from any device with a VNC client.

Why it's safe

  • LAN/VPN only — x11vnc binds to the host network interface. There is no public internet exposure. Access requires being on the local network or connected via VPN.
  • VNC password protected — configured via VNC_PASSWORD environment variable in docker-compose.yml.
  • Non-root process — Joplin, Openbox, and x11vnc all run as the unprivileged joplin user inside the container.
  • Pinned versions with SHA256 verification — both the Joplin .deb and base image are pinned and checksummed at build time.

Stack

Component Purpose
Ubuntu 24.04 Base image
Joplin Desktop Note-taking application
Openbox Minimal window manager
Xvfb Virtual framebuffer (headless X server)
x11vnc VNC server exposing the virtual display
xfce4-terminal Terminal emulator
Thunar File manager
xfce4-taskmanager Process/resource monitor

Persistent storage

Joplin config and data live in a Docker named volume (joplin-config) mounted at /home/joplin/.config. This survives container restarts and rebuilds. S3 sync provides offsite backup and keeps the container in sync with other Joplin installations.

Connecting

  1. Connect a VNC client to <host-ip>:5900
  2. Enter the VNC password (VNC_PASSWORD in docker-compose.yml)
  3. Right-click the desktop for the application menu

Updating Joplin

  1. Update JOPLIN_VERSION and JOPLIN_SHA256 in docker-compose.yml
  2. Get the new SHA256: wget -qO- https://github.com/laurent22/joplin/releases/download/vX.X.X/Joplin-X.X.X.deb | sha256sum
  3. Rebuild and redeploy
10

I've uploaded the current version of jarly here : Package jarly · GitHub

please be aware that this is a very early version.

Configuring your docker container requires the following environment variables:

environment:
- JOPLIN_SERVER=https://joplin-server.invalid/
- JARLY_LOGIN_MODES=SSO,CREDENTIALS

If you want to use SSO you have to run joplin and jarly on the same domain, so jarly can reuse the joplin session id. Using CREDENTIALS for login, you can login with your jopling credentials.

The source code is available here :

see also here : Jarly - a light web client for Joplin