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

changes to compose file not propagated on restart #3

Open
bdentino opened this issue Nov 5, 2015 · 0 comments
Open

changes to compose file not propagated on restart #3

bdentino opened this issue Nov 5, 2015 · 0 comments

Comments

@bdentino
Copy link
Member

bdentino commented Nov 5, 2015

original yml contents are cached and used to restart the service. Need to intelligently relaunch services when their compose files change (remove deleted services, watch/unwatch changed volumes, load new externals, etc). Until the code is a little more organized though, this is gonna be more complicated than it's worth i think.

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