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

Consider providing ability to override volume mount default behavior #167

Open
scotthelm opened this issue Jan 24, 2022 · 1 comment
Open

Comments

@scotthelm
Copy link

For larger projects or mono-repos containing many directories that have self-contained functionality, it would be nice to have a way to specify which director(y|ies) to load. This would potentially decrease the amount of files that must be mounted into the container, required or imported by interpreted languages such as ruby or python, and therefore decrease the startup-time of the container. Perhaps something like nib run-dir <list/of, paths/to/load> <service-name>

@johnallen3d
Copy link
Contributor

I like the idea of improving developer workflow (e.g. performance) in projects like you describe. Before we try to implement a feature here though, I wonder if it's worth considering an approach like what's described in this post.

https://iwpnd.pw/articles/2021-05/docker-compose-in-monorepos

tl;dr — have a top-level docker-compose.yml that defines the shared services (e.g. databases) and a docker-compose.yml in each component directory that extends the parent to pull in the db's.

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

No branches or pull requests

2 participants