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
We are attempting to migrate our Cosmos configuration to a docker based environment. However there seems to be some internal variable that assumes the configuration is in the /cosmos directory. If I use another directory the command telemetry server works fine but all of the screens we have developed try to load from a /cosmos base. For now we are mounting our config at the /cosmos directory as a workaround.
The text was updated successfully, but these errors were encountered:
My expectation was that I could keep my current project folder structure and run it in the container using ruby Launcher from that folder. I'm not that versed in Docker best practices but I guess I don't see why using a docker container would suddenly limit my ability to structure my projects folders which work with any native or vm install of Cosmos.
If you are building your own docker image based off of this one, then you just need to modify the Dockerfile WORKDIR to be wherever your project is located inside the container
We are attempting to migrate our Cosmos configuration to a docker based environment. However there seems to be some internal variable that assumes the configuration is in the /cosmos directory. If I use another directory the command telemetry server works fine but all of the screens we have developed try to load from a /cosmos base. For now we are mounting our config at the /cosmos directory as a workaround.
The text was updated successfully, but these errors were encountered: