You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In previous work I have used docker-compose with mounting of git repositories to facilitate development, and imagine a similar workflow could be achieved with podman. In the development of either the bluesky or databroker stacks I imagine the need for:
Server running in one container, with reload enabled for development
Client running in another container with reload enabled for development
Server to combine the server and client behind a single port (probably NGINX)
There would be a (probably default) production version where it would not enable reload, and would simply build the web application into an optimized static bundle using everything within the container/image.
The text was updated successfully, but these errors were encountered:
I think that would be reasonable, or environment variables for the ones you want (any person is likely to only develop one or two at a time). So a prefix for all repos and/or individual paths I think would work best.
In previous work I have used docker-compose with mounting of git repositories to facilitate development, and imagine a similar workflow could be achieved with podman. In the development of either the bluesky or databroker stacks I imagine the need for:
There would be a (probably default) production version where it would not enable reload, and would simply build the web application into an optimized static bundle using everything within the container/image.
The text was updated successfully, but these errors were encountered: