ProGet Documentation

ProGet Manual Installation

Manual ProGet Installation

These manual installation instructions for ProGet are primarily for load balanced and high availability installations. If you aren't using these features, you should probably use the installer.

ProGet consists of 3 main deployable components:

  • Web Application – an ASP.NET 4.0 web application which serves as an interface to ProGet and serves the NuGet API
  • Service – performs indexing and other background tasks; hosts the web application if IIS is not used
  • Database – a SQL Server database which contains all of the persistent data including feeds and privileges

Installation

Prior to installation of ProGet, a ProGet "home" directory needs to be created, such as C:\ProGet

For the remainder of these instructions and simplicity, we will use C:\ProGet as the root - replace with the specific path you have chosen for your installation as necessary.

ProGet's Identity

ProGet may be configured to use its own domain account or may run as Network Service as long as the account has read/write access to the packages directory.

Database Installation

  1. Create a database called ProGet on the desired server
  2. Unzip ProGet-DbChangeScripts.zip into any directory an run the executable and select option 3 (update). Note: if you are not running SQL Server using the Default Instance or you are not running the .exe on the same server as the database engine, you will have to manually update the connection string within the bmdbupdate executable by choosing option "C" prior to updating.

Service Installation

  1. Create a directory named Service\ under C:\ProGet\
  2. Unzip ProGet-Service.zip into C:\ProGet\Service\
  3. Edit ProGet.Service.exe.config to ensure the following setting:
    • InedoLib.DbConnectionString (if on remote server or different instance)
  4. Install the service. To do this, run ProGet.Service.exe and display help to discover the arguments for the "install" option. Administrator elevation is required to install the service and reserve URLs for self-hosted installations. If you do not reserve a URL the integrated web server will not be enabled.

Web Application Installation

The web application may be hosted either by IIS or self-hosted by the integrated web server hosted by the service depending on how the service was installed above.

  1. Create a directory named WebApp\ under C:\ProGet\
  2. Unzip ProGet-WebApp.zip into C:\ProGet\WebApp\
  3. Edit Web.config to ensure the following setting:
    • InedoLib.DbConnectionString (if on remote server or different instance)

For IIS hosted applications, there are 2 additional steps:

  1. Create an application pool in IIS to run under the appropriate identity; for IIS7 and later, a classic (non-integrated) pipeline must be used
  2. Create a website that points to C:\ProGet\WebApp using whichever host name configuration or ports preferred. Note: A virtual directory is not supported at this time. Note: If IIS6 is used, verify that the website is configured for ASP.NET 4.0.