Migrate Gitpod to Space dev env.
Hello everyone,
I am currently exploring the possibility of standardizing our development process on Space. It would be used to replace Gitpod, Jira, and ChipperCI.
However, I have some issues that I believe stem from my misunderstanding. The entire ticket, deployment, and job aspects are clear.
When it comes to the cloud-based development environment, things get more complicated. From what I understand, we need to create a custom Docker image with our tools, and then use a warm-up script to compile our resources and prepare a few things related to the project's root directory.
Up to this point, everything is fine. Where it starts to become problematic is when I initiate the remote development environment. The terminal in my PHPStorm is that of my local PC, which is a significant issue for manually triggering a compilation with 'npm run build' or performing other actions that a normal developer would do on their PC. I haven't found any solution to this aspect yet. The only thing I can see is that we need to set up additional Docker containers to access the terminal. Do you have any advice?
Another issue is with Gitpod. I love the public URL feature; it allows us to quickly demonstrate progress directly in the developer's environment. How can I achieve the same functionality with Space's development environment?
Thank you for your responses.
Please sign in to leave a comment.
Gregoire Ohanessian Hi,
Services/tools or executable files can be interacted throw the terminal opened directly from the IDE used in the remote Dev Environment. E.g. the "npm" tool comes within the default image used for RDE. Thus, it is possible to open the "terminal" view in PhpStorm launched by RDE and run npm commands. In case you need to run a service container inside RDE, this can be done by using Docker.
It is possible to use a port-forwarding feature to expose the work done in RDE. But it will be available only on your local PC. An alternative would be to use such a service as ngrok inside the RDE and expose the endpoint publicly. It can be used as a temporary solution until "SPACE-15813 Expose http endpoint from dev environment to outter world" is available in RDE.
Great, thank you very much for your response. However, you might think I'm being silly :), when I open the terminal of my remotely connected IDE, I end up on the local computer. And I don't have any other terminal available. I think I missed something in the configuration, but I can't find anything about it in the documentation.
Oleg Beriashvili do you have an idea for my problem?
Thank you for your answers.
Hello Gregoire Ohanessian,
Thank you for the updates! This is not expected behavior indeed. Could you please let me know how the RDE session is getting launched and what version of the IDE is used? I can't reproduce the issue locally. Will appreciate if you can share additional customization done to the RDE instance (if any).
hi Oleg Beriashvili,
here's the config file, it's a test project. Updatechannel EAP and Release not working.
Launched from space application with gateway for phpstorm.
it works on fleet, but fleet is not a workable solution at the moment :) :
Oleg Beriashvili problem fixed :) I've uninstalled all my plugins, I think the problem is with duckly.
Thank you.