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

Add optional flag, so container is not starting with all "fig up", but only on manual demand #912

Closed
sielaq opened this issue Feb 1, 2015 · 5 comments

Comments

@sielaq
Copy link

sielaq commented Feb 1, 2015

It would be awesome to have "optional: true" in fig.yml,
so container is not starting with when "fig up" / "fig up -d" is executed.
but only when you do "fig up " / "fig up -d "
It sould not affect current config so default is "optional: false"

Then you can have multiple versions / alternative solutions /
some specific containers for specific purposes, that are not starting by default.

@thaJeztah
Copy link
Member

I think this relates to, or is a dup of #630 (and related issues)

@sielaq
Copy link
Author

sielaq commented Feb 1, 2015

hmm you mean initial_scale: 0 or scale: 0
sound like a good alternative

@sielaq
Copy link
Author

sielaq commented Feb 1, 2015

but with second thought it is not a goog idea with scaling - then manual run would overrive scale option ?
What if optional container also need to be scaled?

@thaJeztah
Copy link
Member

Good point, not sure. I think right now you would be able to do fig up -d <service-a> <service-b> .... to only start those services. But this can be cumbersome for a large amount of services :D

@bfirsh
Copy link

bfirsh commented Aug 20, 2015

Thanks for the suggestion! I've created an issue here to aggregate many similar suggestions: #1896

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

3 participants