The api listens on 127.0.0.1 by default; so yes, local software can connect (see [1]). File pathes for read/writes and execution are not imperatively ordered b

The api listens on 127.0.0.1 by default; so yes, local software can connect (see [1]). File pathes for read/writes and execution are not imperatively ordered by the client, but done declaratively based on the notebook ID. When the toolschains are in docker, the code runs in disposable containers. It would be possible to add creds (for instance, with creds stored in ~/.nodebook.conf); do you think it's mandatory? The cli mode (--cli) does not expose a port, but watches notebooks and outputs them in the terminal (works nicely with $YOUR_EDITOR) --edit-- I guess running this on a remote server through SSH tunnel would workyes, but I think it's safer and easier to version control the notebooks and run them locally. [1] https://github.com/netgusto/nodebook#%EF%B8%8F-a-bit-of-warning-%EF%B8%8F https://github.com/netgusto/nodebook#%EF%B8%8F-a-bit-of-warn...