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 BELUGA_DEPLOY_HOST #9

Open
duckbrain opened this issue Jun 9, 2020 · 0 comments
Open

Add BELUGA_DEPLOY_HOST #9

duckbrain opened this issue Jun 9, 2020 · 0 comments

Comments

@duckbrain
Copy link
Owner

Problem

Currently DOCKER_HOST is abused to provide portainer and portainer-insuecure "protocols".

Docker, of course, doesn't understand these, and they're only useful for deploying. Usually times, users will want a different docker host to deploy to than to build.

Solution

BELUGA_DEPLOY_HOST will used to deploy when running beluga deploy. If not set, it will default to the value of DOCKER_HOST. It will replace the value of DOCKER_HOST when deploying, including setting DOCKER_HOST when running docker commands.

This will preserve backwards compatibility for users already using DOCKER_HOST, but in documentation, we can remove the sanctioning of abusing DOCKER_HOST.

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