-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Option to disable expose of all docker containers #358
Conversation
@emilevauge I'm strangling with default value when configuration file is used. I didn't find the way how to configure viper. I tried |
@s7anley thanks for your contribution! |
Sure, not a problem. |
+1, it would be great if it could be merged before 1.0 release. |
@emilevauge any news regarding own configuration lib? |
The PR is here #403, will be merged soon :) |
@emilevauge thanks for update, I will take a look during weekend. |
Ping ? |
Hi @s7anley , I'm planning to get this PR in the 1.1 releases. Do you think it's possible ? |
Carrying here #514 |
Oh, I'm really sorry guys. Hopefully, next time I will do better work. 2016-07-11 23:02 GMT+02:00 Vincent Demeester notifications@github.com:
|
@s7anley don't worry about it, I'm just carrying it (and fixing conflicts), but it's still your work and your commit 😉. You did a good job 👍 |
Carry #358 : Option to disable expose of all docker containers
In case someone wants to register containers manually.