-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker image #75
Comments
I'd love to see docker support, recently I tried to make up package for Sorry for the occasional ramble, just wanted to highlight that docker-based version would be helpful to at least some people. |
I would like to try a docker-based version |
Hi @AlexTalker, Good news: we are close to having a big pre-requisite done: a packaged browser Blueprint application, that can easily be included in a Docker image: #168 |
Great news for us! I hope you'll be able to work like you want on this great project and be able to provide a docker image. Have a good day and thanks everybody for all |
This comment has been minimized.
This comment has been minimized.
Good news: The default container from the Theia app repo is published here by a contributor: |
This still being worked on? |
Yes, I've started to prepare a Blueprint Docker Image here: https://github.com/eclipsesource/theia-cloud/blob/main/demo/dockerfiles/demo-theia-docker/Dockerfile This uses this branch at the moment: https://github.com/eclipse-theia/theia-blueprint/tree/jf/docker Open topics are therefore |
* create a dedicated browser application * adapt product so that frontend code is useable from browser app as well * move electron:rebuild to laters stage to avoid conflicts between both applications * Create Dockerfile with Github Workflow and adapt Readme Signed-off-by: Johannes Faltermeier <jfaltermeier@eclipsesource.com>
* create a dedicated browser application * adapt product so that frontend code is useable from browser app as well * move electron:rebuild to laters stage to avoid conflicts between both applications * Create Dockerfile with Github Workflow and adapt Readme Signed-off-by: Johannes Faltermeier <jfaltermeier@eclipsesource.com>
* create a dedicated browser application * adapt product so that frontend code is useable from browser app as well * move electron:rebuild to laters stage to avoid conflicts between both applications * Create Dockerfile with Github Workflow and adapt Readme Signed-off-by: Johannes Faltermeier <jfaltermeier@eclipsesource.com>
* Update repository structure and adapt headings in readme
* Align used plugins * Keep vscode.git
* Add browser app start instructions
* Update repository structure and adapt headings in readme * Align used plugins * Add browser app start instructions * add rate limits for plugin downloads
* Remove updater from browser app
* Try to fix javascript out of heap errors in windows workflow
* Try to fix javascript out of heap errors in windows workflow
* create a dedicated browser application * adapt product so that frontend code is useable from browser app as well * move electron:rebuild to laters stage to avoid conflicts between both applications * Create Dockerfile with Github Workflow and adapt Readme Signed-off-by: Johannes Faltermeier <jfaltermeier@eclipsesource.com>
* Update repository structure and adapt headings in readme * Align used plugins * Add browser app start instructions * add rate limits for plugin downloads
* Remove updater from browser app
* Try to fix javascript out of heap errors in windows workflow
Feature Description:
Before Theia joined the EF, we had the theia-apps repo. Because of its popularity and diversity of contributors, it's a hard repo to re-license, making it difficult to bring under the Foundation.
However, with the move to vscode extensions to support programming languages, it's becoming less important to have multiple, per-language examples, when the main difference is which extensions are bundled. They could essentially all use the same Theia application, in theory.
I think the theia-apps examples can remain, with minimal maintenance, for a while. But we can also make one or a couples, based on our experiences with theia-apps and the lessons learned there.
Let's start with a modest image, a Blueprint-based IDE appliance, for JavaScript/TypeScript software development.
Let's re-use the browser package we'll make in #74
The text was updated successfully, but these errors were encountered: