Skip to content

Conversation

ferventcoder
Copy link
Collaborator

@ferventcoder ferventcoder commented May 6, 2018

Added instructions starter for organizational/internal use of these
scripts. Additionally added notes for folks that may want to take
advantage of Chocolatey but may not have administrative access on
their machines.

This also provides links for learning more, including how to take
advantage of Chocolatey's infrastructure and tools with the open
source edition and without any costs.

Relates to #7

@ferventcoder
Copy link
Collaborator Author

@yodurr Apologies, I didn't notice that it remove trailing spaces when creating the commit. If that is not okay, I can split into two commits.

@ferventcoder ferventcoder requested a review from yodurr May 6, 2018 17:02
@ferventcoder
Copy link
Collaborator Author

Split to two commits to catch the trailing whitespace.

README.md Outdated
choco source add --name="'internal_file_share'" --source="'\\fileshare\chocolatey'" --priority="'2'" --bypass-proxy
#TODO: Add other sources here
~~~
1. Alternatively, you could add the following to the end of all of the package installation/upgrade calls:
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't like that the count is starting over.

README.md Outdated
~~~powershell
--source="'location_name[; location_uri]'"
~~~
1. Unfortunately, you may not be able to take advantage of the one-click installer that are available in the "How to run the scripts" section above. You can still use [an alternative means of running those scripts](http://www.boxstarter.org/InstallingPackages) that still works quite well! Please see the note below for additional addendums.
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Starts over here as well. Markdown with fenced code blocks is sometimes hard to get it to recognize this is not a start over place.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to try something here.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sweet, looks like it worked, pushing the other fix as well.

@ferventcoder
Copy link
Collaborator Author

@mwrock if you can take a look at this and validate it as well for Boxstarter, that would be great!

## Working with Chocolatey for Organizations?
No problem, you can still use these scripts. You'll need to modify the script to reference your internal package store. Here are instructions for doing so:
## Working with Chocolatey in an organization?
Does your organization have strong policies against using the internet? Are you deploying software in air-gapped networks? No problem, Chocolatey is [an offline solution that has zero call home](https://chocolatey.org/security#chocolatey-client), and the best part is you [can create packages and host them internally for free]((https://chocolatey.org/docs/how-to-setup-offline-installation)) (see [What is Chocolatey?](https://chocolatey.org/docs/getting-started#what-is-chocolatey) and [Set Up Chocolatey for Organizational/Internal Use](https://chocolatey.org/docs/how-to-setup-offline-installation)). Yes, you read that right, you can take advantage of Chocolatey's infrastructure without any cost! It is important to point out that Chocolatey itself installs with the [Community Package Repository](https://chocolatey.org/packages) already set as a default source repository to allow ease of installs for the greater community, but it is a simple adjustment to remove that and add your own internal sources.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Chocolatey "has" an offline solution...

Copy link
Collaborator Author

@ferventcoder ferventcoder May 6, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Semantics here - Chocolatey is a fully offline solution that is installed with a community repository that is on the internet. The sources themselves and the packages are what determine internet access.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I digress tho - if you prefer it to say "has", I can make that adjustment.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarified the point above.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see... perhaps say "the Chocolatey client"

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like that better!

@yodurr
Copy link
Contributor

yodurr commented May 6, 2018

I'm thinking we need a separate md for organizational use details and use the Readme for an intro.

Add instructions starter for organizational/internal use of these
scripts. Additionally added notes for folks that may want to take
advantage of Chocolatey but may not have administrative access on
their machines.

This also provides links for learning more, including how to take
advantage of Chocolatey's infrastructure and tools with the open
source edition and without any costs.
@ferventcoder
Copy link
Collaborator Author

@yodurr sounds good, but I'm at the end of my time for this morning. I can jump back in later tonight or tomorrow to provide that split.

@yodurr
Copy link
Contributor

yodurr commented May 6, 2018

No worries - I can bring this in today, make the split, and we can resume edits later. Thanks Rob!

@yodurr yodurr merged commit 6f37693 into microsoft:master May 6, 2018
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