Efficient developer workflow VSC

[Ben Falchuk]

Hi forum! I'm a relative newbie but have been successfully building and deploying a Flask webapp in Google Cloud Run, using (exclusively) Visual Studio code and its GC extension(s) on Win10.  I have a good quad core laptop and fast Internet. I notice that my webapp dev workflow is hampered by the lengthy "rebuild" process (e.g., each time i make an edit - say to an html page in my Flask webapp - and save it, Google Cloud Run extension in VSC takes it as a cue to rebuild for me; that's fine in principle. But the Minikube and the Docker is re-built from ground-up and launched in the Emulator; this takes on the order of minutes).

My question is: is there a short-cut I don't know that will let me make "hot changes" - say to HTML or JS files in my Flask app - and have the associated parts within my Cloud Run Emulator image also update? (e.g., to CSS, JS or HTML files). A reload on the local port (often :8080) would then - desirably - show me those changes.. 

On a related note, i know that its likely not possible to 'exec bash' into the Cloud Run docker itself to make changes.

thx.

[Horace (Cloud Platform Support)]

Hello,

Hot reload after code changes is supported however building with a Docker file, a complete rebuild and redeploy will happen which in turn may not be as fast. Additionally, it should be available if you choose to run without debugging mode [1]. 

Can you kindly try to uninstall and reinstall the extension or try coding on a different machine to compare the performance. Lastly, I suggest to contact the team directly [2] for further information.

Regards

[1] https://github.com/GoogleCloudPlatform/cloud-code-vscode/issues/356

[2] https://github.com/GoogleCloudPlatform/cloud-code-vscode/issues

[Ben Falchuk]

Thanks, I understand a *bit* better now.. I think that essentially my Docker/requirements are a long list of "pip installs", so rebuilding the Docker is the time suck in my process after each minor change/save. Restating it: i suppose i'm seeking a way to get hot-changes working for the app running *inside* the docker.. - e.g., changing a Flask web page and rebuilding/restarting only Flask in the running container (not re-building the whole Docker from scratch).