Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot install our Cosmos configuration to a different directory #3

Open
DKlaren opened this issue May 14, 2020 · 3 comments
Open

Cannot install our Cosmos configuration to a different directory #3

DKlaren opened this issue May 14, 2020 · 3 comments

Comments

@DKlaren
Copy link

DKlaren commented May 14, 2020

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.

@ghost
Copy link

ghost commented May 21, 2020

Mounting your config directly at /cosmos is exactly how this Docker image is designed to be used. How would you expect it to work differently?

@DKlaren
Copy link
Author

DKlaren commented Jun 9, 2020

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.

@ghost
Copy link

ghost commented Jun 9, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant