Joplin Web API for Nextcloud

[laurent]

Joplin Web API for Nextcloud is now discontinued in favour of Joplin Server

---

For information, I've started a Joplin API app in Nextcloud there: GitHub - laurent22/joplin-nextcloud: Joplin Web API for Nextcloud

It is not meant to be a Joplin web client, and there's no plan for it to be so. Rather it's to provide an API to allow sharing a note publicly, and maybe later to allow collaboration.

More info on the official website:

https://joplinapp.org/nextcloud_app/

[sciurius]

Excellent!!

I get this build error:

tar: The following options were used after any non-optional arguments in archive create or update mode.  These options are positional and affect only arguments that follow them.  Please, rearrange them properly.
tar: --exclude-vcs has no effect
tar: --exclude ‘../joplin-nextcloud/build’ has no effect
tar: --exclude ‘../joplin-nextcloud/tests’ has no effect
tar: --exclude ‘../joplin-nextcloud/Makefile’ has no effect
tar: --exclude ‘../joplin-nextcloud/*.log’ has no effect
tar: --exclude ‘../joplin-nextcloud/phpunit*xml’ has no effect
tar: --exclude ‘../joplin-nextcloud/composer.*’ has no effect
tar: --exclude ‘../joplin-nextcloud/js/node_modules’ has no effect
tar: --exclude ‘../joplin-nextcloud/js/tests’ has no effect
tar: --exclude ‘../joplin-nextcloud/js/test’ has no effect
tar: --exclude ‘../joplin-nextcloud/js/*.log’ has no effect
tar: --exclude ‘../joplin-nextcloud/js/package.json’ has no effect
tar: --exclude ‘../joplin-nextcloud/js/bower.json’ has no effect
tar: --exclude ‘../joplin-nextcloud/js/karma.*’ has no effect
tar: --exclude ‘../joplin-nextcloud/js/protractor.*’ has no effect
tar: --exclude ‘../joplin-nextcloud/package.json’ has no effect
tar: --exclude ‘../joplin-nextcloud/bower.json’ has no effect
tar: --exclude ‘../joplin-nextcloud/karma.*’ has no effect
tar: --exclude ‘../joplin-nextcloud/protractor\\.*’ has no effect
tar: --exclude ‘../joplin-nextcloud/.*’ has no effect
tar: --exclude ‘../joplin-nextcloud/js/.*’ has no effect
tar: Exiting with failure status due to previous errors
make: *** [Makefile:131: appstore] Error 2

[foxmask]

may be you could create a new dedicated topic, I think guys won't come here now with this new wonderful project

[laurent]

@foxmask, I’ve moved it here and clarified the goal since it’s not the same as your project.

[foxmask]

[laurent]

@sciurius

I get this build error:

It's a prototype and won't work on its own as it's an API. It will be connected to the Joplin clients to provide sharing, etc.

[Shamp0o]

As a Nextcloud user I like the idea but I’m not sure if it’s the right design decision as it only caters to Nextcloud users. Sharing notes (either publicly or for collaboration) is quite an essential feature in my opinion which, once added, lots of user will want to use.

Are there any news about the Joplin Server you started to work on some weeks ago?

[laurent]

Both approaches have the same disadvantages actually. With Joplin Server, it would manage sharing, etc. but it will also need to manage your sync items, so you can’t use it next to Dropbox, Nextcloud or anything - it’s an all or nothing.

With the Nextcloud app, it’s similar, you can only use it with Nextcloud but of course, many more of Joplin users already have Nextcloud so it’s less of an issue. If you already have Nextcloud, it’s also very easy to install - you just press a button and it’s done.

So in the end, it was making more sense to make a Nextcloud app. Also it already handles user authentication, file access, sharing, database and other features needed for this, so it’s also a lot less effort.

[Shamp0o]

You’re completely right. I guess it just “felt” more natural to me to have a dedicated server which would be the recommended way to sync and a couple of alternatives with a limited set of features.
In this scenario Nextcloud takes the spot of the recommended way to sync.

I’m glad this is being worked on.

[laurent]

@Shamp0o

In this scenario Nextcloud takes the spot of the recommended way to sync.

Yes I believe though. I'm developing it in such a way that the Joplin stuff is decoupled from the Nextcloud backend so that potentially the app could be used separately (for example on an Apache or Nginx WebDAV server), but initially it will just be for Nextcloud. Dropbox and OneDrive unfortunately won't be supported I think.

[steve28]

would this allow something like rest_uploader to upload directly nextcloud? I.e., does it expose the webclipper API?

[laurent]

@steve28

would this allow something like rest_uploader to upload directly nextcloud? I.e., does it expose the webclipper API

No, as a general rule if something can be done by the desktop (or mobile) client that's how it will be done. So if OCR is ever supported it will be part of the desktop app.

[PackElend]

I have just noticed that the topic was split.
I'm currently updating the GSoC application. In the course of this, I would like to publish the first project idea.
Porting the web-app or have a Nextcloud app created would be the idea.
Now we have this here
In general, it is needed

• storage
• back-end server (what may run within another application)
• front-end apps

Regarding Nextcloud

1. is it smart to run the back-end as an app in Nextcloud
2. shall it be installed on the same server (as e.g. docker image)
3. an app is written what communicates via the API
4. port (fork) the web-app, to make it run as nextcloud app

Currently, I don't know how to describe the project(s) .
Whatever going to happen, it should be done in such a way that Joplin is not limited to be used with Nextcloud only, when you want to integrate it into another collaboration app.
Of course, Nextcloud would be the pilot and thus the one with the most drive most likely.

description should be as described in

Internal URL/hyperlink

I don’t think there’s a special format but it could simply be a Markdown file with these sections: Abstract: in 2-3 lines, what the project is about, why it’s needed. Specifications: as much details as possible about the feature. I think your post above is pretty much it. External links: a link to the discussion here, or any other link you can find related to the feature. As I understand, they want to see that there’s interest around the feature and discussions happening so that would b…

[Shamp0o]

I installed the pre-release of Joplin that adds note sharing capabilities. I also installed the Nextcloud app. When I check the status via sync settings in Joplin I get “Beta: Joplin Nextcloud App status: OK”. When I share a note, the fields in the Nextcloud app populate. Opening the public share link, however, results in a 404.

[laurent]

If you click on the Joplin icon in Nextcloud, what does the status page says? Is there a sync target and “share” row?

[Shamp0o]

[laurent]

Hmm, that’s weird. Could you post a screenshot of the 404 error too please? It seems to be Nextcloud that can’t find the page then. Also what’s the URL you get for sharing? (you can remove the domain name)

[Shamp0o]

Sharing generates the following URL:
https://cloud.example.com/extra-apps/joplin/shares/dp7OHmRJYAwS7FknDD2gdP

My Nextcloud instance is based on the snap package. The Nextcloud version is 16.0.5.

[laurent]

@Shamp0o

Sharing generates the following URL:
https://cloud.example.com/extra-apps/joplin/shares/dp7OHmRJYAwS7FknDD2gdP

The "extra-apps" part is strange as normally apps are under just "apps". Does it work if you change this part to "apps"? As in:

https://cloud.example.com/apps/joplin/shares/dp7OHmRJYAwS7FknDD2gdP

[Shamp0o]

It does not.
However changing it to https://cloud.example.com/index.php/apps/joplin/shares/dp7OHmRJYAwS7FknDD2gdP (include index.php) works.

At first glance there are a couple of issues with the rendered markdown (which I guess is to be expected at such an early stage):

• Bullet points don’t work
• Checkboxes don’t work
• Images are not shown
• Hyperlinks have no visual cue
• File-attachments have no visual cue (like blue font color)
• File Attachments have no visual cue and direct me to my Nextcloud files-page
• [toc] doesn’t work