Home / GitHub Page

Web Clipper API for CLI


#1

In the design document is written that both desktop and cli should be able to start a web clipper server.
Am I correct to notice that the cli doesn’t support this yet?
Are there concrete plans to add this?


#2

At the moment, only the desktop app runs the service.


#3

@sciurius FYI:

@laurent this would be a nice feature. the only problem could be, if both (desktop and CLI app) are running at the same time. This has to be guarded somehow.


#4

If they both use port 41184 only one can be active at a time.


#5

@sciurius I’m aware of that. That’s why I said it had to be guearded. :wink:


#6

In my setup all Joplin clients sync with a cloud (ownCloud) server. This makes it tempting to consider the cloud as the authorative repository for the notes. So a headless Joplin content server (that directly communicates with the cloud) running as a daemon would allow all kinds of (authorized) apps to exchange notes with Joplin.


#7

For this, couldn’t you use the desktop app in the background? You could set it up to start minimised in the system tray and make it auto-start with the system. Wouldn’t that work?


#8

Yes, except for a few details:

  • I must not exit the app (as I’m used to).
  • I’m not yet sure how many resources a resident Jopin will take.
  • It cannot run headless on a server.

As a first step, yes, this is fine. For more serious purposes a real headless server would still be better.


#9

I see what you mean and I expect it’s easy to enable this since the desktop and CLI apps share most of the same boot code. https://github.com/laurent22/joplin/issues/834


#10

Exactly my problem. I’d like to run it in an Ubuntu Server.


#11

I’ve started looking at it here but I’m wondering what would be your use case for the headless server? Is it so that you can host it somewhere and then access it from anywhere over the internet?


#12

For me the use case would be to run the joplin server on a NAS, together with the ownCloud server that stores the notes. Or maybe on a small server like RaspberryPi.


#13

@laurent I don’t really want it accessible over the 'net. I’d only expose it to the local host. Then I can have a façade in front of it, that’ll let me create a note (and maybe append to an existing one).

That is, the one thing I still have set up with IFTTT and Evernote is that some stuff gets appended to a few notes, and occasionally a new one is created. Can’t do that with Joplin yet. But I definitely will not expose any interface that’ll allow reading of the notes.

Side note: not sure if you’ve read the discussion elsewhere, but I’m hoping I could maybe use Huginn for the façade, without having to write anything myself. If not, I do have an app already running that I could quickly update. (I want to avoid hosting a new service because of it, though.)


#14

you spoke of it with me here :wink:


#15

I know. That sentence was aimed at Laurent, though. :wink:


#16

Oh dear. Hopefully, one day I get to understand all these techy terms and make a more meaningful contribution to this wonderful app. :blush:


#17

Thanks for the feedback, I wonder if it would make sense to convert it to a server right away, with auth, etc. so that it can be used remotely.


#18

That would open many possibilites. We could then create share sheets for mobile devices etc.


#19

One lingering doubt remains: even in the scenario I’ve described, I’m still not sure I’d be able to handle the encryption satisfactorily. As it is, I’d have to sync all my notes into the server where they’d be in plain text - even though it’d be unnecessary for its actual job. Perhaps I’ll try a different approach.