Has anyone figured out a way to get this to work anywhere other than localhost?

[JellyKid]

It looks most everything has been hard-coded to the localhost for some reason. Not everyone has docker locally or the capability to run containers locally, especially in very secure environments. I've been trying to figure out ways around this like a reverse proxy or running a container with a browser in the same "compute" network but a lot of things are still broken. Is there a recommended way to break this tutorial out of localhost jail?

On that front, does everything need SSL enabled to work? I was thinking about disabling SSL on everything so I could do a reverse proxy /w rewrite that adds SSL but it's going to run into issues if everything underneath is using SSL.

[johrstrom]

Is there a recommended way to break this tutorial out of localhost jail?

Not that I'm aware of, but even so, I don't think I'd advise deploying this somewhere that's available over the network. All the users passwords are known/documented on these READMEs.

I'm sure it's possible through the ood_portal.yml servername and certian docker compose options (like --net=host), but again, not advisable the username/password combinations are known to anyone.

On that front, does everything need SSL enabled to work?

I think most things should work over plaintext.

[JellyKid]

I don't think I'd advise deploying this somewhere that's available over the network. All the users passwords are known/documented on these READMEs.

I'm not planning on deploying it into production just somewhere on-prem where key stakeholders can evaluate and compare it to what we are currently using. More of an early stage POC. A lot of our development happens on remote servers. Most non-dev workstations are not really powerful enough to run a bunch of containers not to mention granting admin access and other security relate issues. I guess I could just stand up a VM with a desktop and VNC....

[johrstrom]

I guess I could just stand up a VM with a desktop and VNC....

If you stood up a VM you could get Juptyer and Rstudio to work without having to install additional things on your compute cluster. Or use launch the desktops through containers so you don't have to install more on your compute nodes.