Joplin Web - Web application companion for Joplin

So if its the same error with curl, this error is not related to the app

What Joplin terminal version are you using ?

It’s related to the davfs mount because, I copied the data from my webdav server locally I have not this issue with the token.

Here is my joplin version :

pi@Ploutos:~$ joplin version 
joplin 1.0.149 (prod)

May be another path ot look for, I already have a service on port 8080 on this machine. When I start the vue I have the following prompt :

pi@Ploutos:~/joplin-web/joplin-web$ 
> joplin-vue@0.2.0 serve /home/pi/joplin-web/joplin-web/joplin-vue
> vue-cli-service serve --mode development --host 0.0.0.0 --port 8080

Joplin Web - Starlette powered
sh: 1: vue-cli-service: not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! joplin-vue@0.2.0 serve: `vue-cli-service serve --mode development --host 0.0.0.0 --port 8080`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the joplin-vue@0.2.0 serve script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2019-10-25 10:00:16,024 - INFO - Started server process [22378]
2019-10-25 10:00:16,025 - INFO - Waiting for application startup.
npm2019-10-25 10:00:16,027 - INFO - Uvicorn running on http://0.0.0.0:8001 (Press CTRL+C to quit)
 WARN Local package.json exists, but node_modules missing, did you mean to install?

Yes you need to change this one . I check where. I’m in a Subway;)

Have a look at


To change 8080

You are a hero working on that in a subway :slight_smile: I change to 8090 put i've the same issue on startup joplin-vue.

I think the problem with davfs is not related to the port 8080. I tried again with the davfs mount, with the chowncommand before and I still have an EACCES error when I access the mounted folder. I don't have this error when I use the local data (not the mounted one in davfs).

May be the user that mounts the mount point does not have the right access to the resources folder.?

Hey foxmask,

I make the mount via the mount -t davfs .... command as root. The mount point have the following ls -al entry :

drwxr-xr-x  4 pi   pi       4096 Oct 25 14:09 joplin-desktop

I cannot make the mount as a non-root user. Is there a point I need to fix ?

If I’m not wrong, you should allow the user pi on the server from the folder where you export
Then you could use mount as the user pi from your other computer.

last update :
search engine w/ dynamic result

2 Likes

Possible to run this on a shared webspace?Php, MySql etc available

Hi @foxmask,
I had some quick talks with the nextcould folks about better integrating Joplin into nextcloud. We exchanged only some very basic thoughts on what should be done as an GSoC project what will be hopefully announced by @laurent soon here in the forum.

Inspired by other apps that are integrated as wrapper (Draw.io) or as a fork (Pico).
In addition, building nextcloud apps, Joplin or Joplin Web refers to the same technologies npm (Joplin, nextcloud), VueJS (Joplin Web, nextcloud), node JS (Joplin, nextcloud) and Python (Joplin Web, nextcloud apps writen in Python).

So it is feasible to fork either the Joplin desktop, to make it headless server nextcloud app or may even the Joplin CLI, although there are still challenges:

some help on headless is given on

Hi @PackElend,
What do you expect from Joplin-Web ?

can it be forked to make it nextcloud app?

it’s up to you, but I remind that the project is written in Python and VueJS, not in PHP and won’t be ever.

What can be done (by who wants to fork), is to keep the VueJS part and write the replies of the API calls (actually made from VueJS to Python) in PHP.

my mistake, it is corrected

it just just an idea to avoid to open an enterily new project

What can be done (by who wants to fork), is to keep the VueJS part and write the replies of the API calls (actually made from VueJS to Python) in PHP.

You will aslo need to write Joplin lib for PHP support then the app could make API calls to jolplin

There are nextcloud apps writen in Python) so it would not be start from scratch

if you dig what that apps are, news-updater is not a webapp, and https://github.com/nextcloud/appstore is the app store of nextcloud , not an app for nextcloud. So there is nothing in Nextcloud working as an nextcloud app in python

:pensive: will see what the nextcloud folks are going to say, when the GSoC things kicks-off

As it seems to me that there is no core API to allow external app to “talk” with each other, Nextcloud will stay a full PHP stack language.

may https://github.com/matejak/nextcloud-API helps
or references given in
https://help.nextcloud.com/t/django-or-python-integration-api/9922/5
https://github.com/goodspb/pdlib
https://pypi.org/project/nextcloud_news_updater/