Yes, I was only talking about really just running Sage locally. - Marc.
On Friday, April 26, 2024 at 7:54:38 PM UTC-5 Nils Bruin wrote: > On Friday 26 April 2024 at 15:44:22 UTC-7 marc....@gmail.com wrote: > > I don't see what difference the choice of port makes to a user. It is not > possible to guarantee that the same port will always be used, since ports > are assigned on a first-come first-served basis. Consequently it is not > possible to "bookmark" the address of either a jupyter server or a > cocoserver. The port should be viewed as arbitrary and unpredictable. The > address is always 127.0.0.1 in either case, by necessity. > > > The port number that jupyter tries to use is configurable and there can be > reasons why you'd want to care about it. For instance, if you have a beefy > linux server that students in various locations want to use from windows > workstations. Ideally you'd run jupyterhub on it, but it's a complete > headache to figure out authentication and file system access and probably > impossible to find sysadmins capable and willing to make that setup secure. > > Instead, one could just assign a port number to each individual so that > they can set up a script to start their jupyter server on the right port on > localhost. They then just need to learn to use ssh (via PuTTY, for > instance) to tunnel the particular port from their desktop to the server > and then they can point the browser *on their own machine* to the right > address. It gets around the problem of getting people to install jupyter on > a windows box and it shows them an environment in which they could graduate > to useful work on the server themselves. And mainly, it gets around the > very real problem of getting a JupyterHub server set up. The price you pay, > of course, is that the port number is now very well-defined and actually > quite important. In that setup, it would be nice if the documentation were > served through the web server that jupyter is already running, because > that's the only port that's tunnelled. Or if the documentation just lives > on the internet; that's fine too (because if one weren't in an > internet-facing environment, setting up JupyterHub would at least be less > problematic from a security point of view). > > So, yes, if you're really just running it locally, the port number isn't > so important, but if any port forwarding comes into play, it becomes very > important to know the port number! > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/7c9fbecb-6df0-41b4-9c46-5672e4f26149n%40googlegroups.com.
