Marc Dumais

> He said that we should properly made fully automated CI build but this is not even possible at this stage since Theia is a new app and doesn't have...

Hi @ande8331 , You're right - `ms-toolsai.jupyter` I think was split from the Python extension recently, and is now a dependency. Momentarily it's not on open-vsx, but even if it...

One way forward would be to have the dependent extension, `ms-toolsai.jupyter`, available on open-vsx.org. The extension's source code (1) is licensed under MIT, but the extension itself is under a...

@dwjbosman I think we can start with your suggestion above @satishbabariya I am not sure if we'll get these type of image variant for more than maybe the most basic...

Hi @MarcoGriep88 , At a quick look it seems your image is a fork of our full image. That's not ideal since we now would have 2 images to update...

Hi @MarcoGriep88 > Thanks, I will try this. I am not that experienced with Docker :) No problem - let us know if you have questions or need help.

Hi @jcalfee , Thanks for the suggestion. Would you care submitting a PR e.g. where you update the README examples as per above?

> `localhost` will not work anymore. Its going to have to be 127.0.0.1 .. It works for me on Linux. I don't know about Mac and PowerShell. Hi @jcalfee Thinking...

@jcalfee thank you for the thoughtful arguments. I agree that probably the local use-case is the most popular vs a more intricate setup with a proxy in front to handle...

@dm4tze have you considered starting with one of the more modest images, that would be easier to handle? Like `theia-docker` or `theia-cpp-docker`? The `theia-full` image is quite big (> 4GB)...