search

jjethwa / rundeck

GNU General Public License v3.0
122 stars 137 forks source link

Provide guidance on use behind corporate proxies #54

Closed cosmocracy closed 7 years ago

cosmocracy commented 7 years ago

I found that much trial-and-error was needed to get the Rundeck image to work as desired when there is a corporate proxy between Rundeck and the internet. (This was primarily needed for access to GitHub.com for the SCM plugin.)

If you take a look at issue https://github.com/rundeck/rundeck/issues/1777 you can see some commentary related to the work needed to pass through DNS as well as the proxy variables. I know this is not "rundeck-specific" but sometimes providing guidance like this goes a long way toward boosting adoption and saving your admins/users headaches.

Perhaps an extra section in the README? Or a dedicated Wiki page (linked to from the README)?

jjethwa commented 7 years ago

Thanks @cosmocracy

That's a great idea and thanks for the info Would you like to send a PR with the README update since you did all of the legwork? 😃

cosmocracy commented 7 years ago

Can do!

On Jan 25, 2017, at 5:04 PM, Jordan Jethwa notifications@github.com wrote:

Thanks @cosmocracy

That's a great idea and thanks for the info Would you like to send a PR with the README update since you did all of the legwork? 😃

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

vipulagarwal commented 7 years ago

I ran into this problem and resolved it using your method. I have created a patch for the readme. Please let me know if it is OK to submit a pull request.

jjethwa commented 7 years ago

Hi @vipulagarwal

Thanks so much! Please submit the PR at your earliest convenience 😄

vipulagarwal commented 7 years ago

Np @jjethwa - pull request 91 opened