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

Need an example to avoid corporate network rate limiting. #166

Closed
timothy-mcroy-cengage opened this issue May 6, 2022 · 1 comment
Closed

Comments

@timothy-mcroy-cengage
Copy link
Contributor

Is your feature request related to a problem? Please describe.
The default Example.ps1 config does not include an example to utilize a private NuGet feed to install chocolatey. When folks use the default example, they will run into Chocolatey's HTTP 429 rate limiting if they create too many servers too quickly behind a NAT.

Describe the solution you'd like
Introducing another example that demonstrates how to override the download location.

Describe alternatives you've considered
Possibly hosting a separate install.ps1 script in my local SCM. This isn't the right solution though as both are working around the same problem of DSC relying on external scripts that aren't part of the DSC module. An example of the workaround is more accessible and easier to implement.

Additional context
Example implemented in a fork.

pauby added a commit to pauby/cChoco that referenced this issue May 15, 2022
…kage download location

This environment variable is read by chocolatey.org/install.ps1
pauby pushed a commit that referenced this issue May 16, 2022
…oad location

This environment variable is read by chocolatey.org/install.ps1
pauby added a commit that referenced this issue May 16, 2022
* timothy-mcroy-cengage/development:
  (#166) Add example that shows overriding the Chocolatey package download location
@pauby
Copy link
Member

pauby commented May 16, 2022

This was added here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants