Fix GitPod environment setup
I am NOT a GitPod/Go developer so comments/suggestions/requested changes are welcome.
This PR updates the Gitpod.yml file to run a series of commands before yarn dev to get the environment in the proper state for yarn dev to run successfully.
I am concerned I may have a bug still because while this appears to set everything up properly and the interface does appear, any subsequent code changes don't necessarily get reflected in the running instance as expected. Sometimes they do, sometimes they don't.
It looks as though the hot recompile is sometimes not able to restart the server?
[dev:go] time="2021-12-29T17:37:37Z" level=info msg="listen tcp 0.0.0.0:9998: bind: address already in use"
[dev:go] time="2021-12-29T17:37:37Z" level=fatal msg="listen tcp 0.0.0.0:9998: bind: address already in use"
Sometimes it gives those errors but keeps trying and the changes take affect, other times it just stops trying. Or at least that is what it seems like in the console.
After discussing this in Discord with @CoolMintChocolate it seems that it is normal for it to get in this stuck state and need to be manually restarted. However when the environment is run using yarn dev and the two processes handled by concurrently the user is unable to ctrl-c and restart the server.
Skipping yarn dev and instead starting up yarn dev:ui and yarn dev:go in separate terminal tabs in GitPod allows the user to restart manually then this stuck state is achieved.
I would recommend to remove the auto start of yarn dev from the environment, and update the instructions slightly to indicate to run the two commands manually.
Is this still relevant after the build system changes or should I just close it?