🥳 cloud.jolin.io - A new Pluto deployment, integrated with GitHub

:partying_face: NEW - Jolin Cloud :partying_face:

Pluto.jl for your company

Dear Julia and Pluto enthusiasts,

I am very happy to announce Jolin Cloud.

Awesome Extras on top of normal Pluto.jl:

  • build self-updating notebooks for real-time streaming analysis
  • integrated with GitHub for version control and dev → test →prod automation
  • easily authenticate at AWS, Azure, Google Cloud, or HashiCorp Vault (using tokens)

Jolin Cloud is in alpha phase. Please write me an email if you have any questions.

Stephan Sahm
Founder of jolin.io


Very nice!

1 Like

Sounds cool, but I’m a bit surprised by the level of access I need to give Jolin in order to subscribe :thinking:


Thank you for the reply.
TLDR: Access to private/public repos is crucial for cloud.jolin.io to provide its services. If you don’t want cloud.jolin.io to see your existing repos, you can create a new github user.

How Jolin Cloud requests github rights

cloud.jolin.io currently requests github access tokens with the following scopes:

  • “user repo”

Looking into it, I just changed this to

  • “read:user user:email repo”

Github docs don’t show any useful subscopes for the “repo” scope for Jolin Cloud. Hence this needs to stay.

The changes are already live:

Of course, your credentials are 100% secured from other users access, and I myself and also others working on Jolin Cloud will never use your credentials. They are only used in automated ways for the features of Jolin Cloud.
Also note that you can always reject the permissions for the github access token later on.

But why would Jolin require write access to all my repos? I mean, I wouldn’t give that to anyone :rofl:
Can’t it be on a case-by-case basis?


Please take a look at the mentioned Github docs. Github oauth tokens do not offer this possibility. Restricting access is really best done via the creation of a respective new user.

Note that it is against Github TOS to have more than one free (non-bot) account, so this might be relevant if you are currently using a free account.


Researching more about alternative options, JolinCloud may migrate from being an OAuth app to a Github App in the future. That would offer more fine grained permissions, but the transition is not straight forward, as different APIs are supported by each system, and the documentation misses some parts which are crucial for cloud.jolin.io (hence needs testing, and maybe contact to GitHub itself).

I put it onto the internal development board as a feature request. Thank you @gdalle for bringing this up.


Right, I was asking because I had the experience of apps like codecov.io, to which I give repo-specific read-only permissions. Based on your follow up, it seems codecov might be a GitHub app instead of an OAuth app, which would explain the difference (I wasn’t familiar with the specifics).

I don’t know if I’m alone in this, but creating a new user might be enough of a hurdle to discourage me from using Jolin in the first place… I love Pluto, and I have no doubt that Jolin is an awesome product, I’m just very lazy :rofl:

I appreciate you taking the time!


This is cool! Appreciate you putting out out there.


I am very glad to announce that JolinCloud now runs as a Github App (instead of OAuth app, which it was before). :partying_face:

This allows for much better permission control :slightly_smiling_face: :+1: