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

Apply an HTTP_PROXY for us corporate shills. #1

Merged
merged 1 commit into from
Jul 3, 2013

Conversation

johnbellone
Copy link
Contributor

This helps all of us that are stuck in the corporate world. Use upstart to export an HTTP_PROXY which is specified through the configuration.

This helps all of us that are stuck in the corporate world. Use upstart to export an HTTP_PROXY which is specified through the configuration.
@johnbellone
Copy link
Contributor Author

I read the Upstart documentation and it seems both env and export could have been used here. It should be noted that sudo would reset the environment if we ever performed that here. The documentation that I followed for upstart configuration.

@bflad
Copy link
Contributor

bflad commented Jul 3, 2013

This looks good to me. Thanks for the contribution! I'll also create a node['docker']['http_proxy'] default attribute that is nil and bump the version.

bflad added a commit that referenced this pull request Jul 3, 2013
Apply an HTTP_PROXY for us corporate shills.
@bflad bflad merged commit 2a95fea into sous-chefs:master Jul 3, 2013
@bflad bflad mentioned this pull request Jul 23, 2013
someara pushed a commit that referenced this pull request Feb 19, 2016
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

Successfully merging this pull request may close these issues.

2 participants