On Wednesday, April 8, 2020 at 4:11:05 AM UTC+2, Dima Pasechnik wrote:
>
>
>
> IMHO this is not exposing the server to "open internet", this is
> allowing your client machine (at home), and only it (using "bind
> addess), to access your server --- which, normally speaking, is behind
> a firewa
On Wed, Apr 8, 2020 at 6:18 AM Denis wrote:
>
> Hi Markus,
>
> well, that would be the non-paranoic approach, to put it mildly. Generally
> speaking, it is against best practices to expose the server of a web
> application to the open internet.
IMHO this is not exposing the server to "open inte
Hi Markus,
well, that would be the non-paranoic approach, to put it mildly. Generally
speaking, it is against best practices to expose the server of a web
application to the open internet. This is true even for a CMS like Plone, let
alone Jupyter, which is intended for execution of arbitrary co
Hi Denis, I am not sure if this helps with your use case, but something I
occasionally use to run Jupyter on a remote machine is a command like this:
ssh -L localhost::localhost: REMOTE -t sage -n jupyter --no-browser
--port=
--
You received this message because you are subscribed
