How To Setup the Chocolatey.Server Package
The Chocolatey.Server package contains the binaries for a fully ready to go Chocolatey NuGet Server where you can serve packages over HTTP using a NuGet-compatible OData feed.
Chocolatey Server is a simple Nuget.Server that is ready to rock and roll. It has already completed Steps 1–3 of NuGet's host your own remote feed. Version 0.1.2 has the following additional adds:
- Uses same enhanced NuGet that Chocolatey uses so you can see more information in search if you choose to use those things.
- Allows packages up to 2GB. Package size can be controlled through maxAllowedContentLength and maxRequestLength.
When you install it, it will install the website typically to
Setup with Puppet
If you are using the Puppet module chocolatey/chocolatey_server, it will do all of the additional setup for this package and allow some customization.
The module works with Windows Server 2008/2012.
For a simple
include chocolatey_server it does the following automatically:
- Ensures IIS is installed
- Ensures ASP.NET is installed
- Ensures the chocolatey.server package is installed
- Ensures an app pool for the chocolatey.server site
- Ensures the IIS website is setup for chocolatey.server
- Ensures permissions for the site are set correctly.
- Install or upgrade the package -
choco upgrade chocolatey.server -y
- Ensure IIS is installed. You can try
choco install IIS-WebServer --source windowsfeatures
- Ensure that ASP.NET is installed. Try
choco install IIS-ASPNET45 --source windowsfeatures(
IIS-ASPNETfor Windows 2008).
- Set up an app pool for Chocolatey.Server. Ensure 32-bit is enabled and the managed runtime version is
- Set up the IIS website pointed to the install location and set it to use the app pool.
- Go to explorer and right click on
c:\tools\chocolatey.serverand add the following permissions:
IIS APPPOOL\<app pool name>- Read
- Right click on the
App_Datasubfolder and add the following permissions:
IIS APPPOOL\<app pool name>- Modify
Looking for where the apikey is and how it is changed, that is all done through the web.config. The config is pretty well-documented on each of the appSettings key values.
To update the apiKey, it is kept in the web.config, search for that value and update it. If you reach out to the server on https://localhost (it will show you what the apikey is, only locally though).