-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Speed up edit-compile-run loop for workspace components #9569
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is awesome! thank you! ❤️ ❤️ 🦸
Awesome ❤️ |
💯 |
@roboquat How do you run debug.sh? Is this for a gitpod user or a gitpod developer? Is there anything like this for developing dockerfiles? |
@mteam88 Hi, these scripts were designed for the gitpod developers. |
@utam0k Ok then. Any way currently to simulate the build process that occurs when starting a workspace so one doesn't have to create a new workspace after every change to a .gitpod.Dockerfile? |
@mteam88 Good question! Thank you. But there is no such thing as far as I know. Maybe these documents will help you. |
@utam0k Checked those out.
Is sorta useful, and is essentially what I have been doing, but it does not completely simulate starting a workspace. My project (based on the workspace-vnc-full gitpod image) requires that. Rather annoying to start a whole new workspace. And recently I have had problems with that build system link to discord issue |
@mteam88 Nice idea. I missed your discord question. If you want, you can create the issue with the minimal reproduction method you found. |
@utam0k Will do. Thanks for all your help! |
@mteam88 Thank you! |
Description
Speed up edit-compile-run loop for workspace components. Each workspace component has a script that will
Related Issue(s)
n.a.
How to test
Release Notes