- 11 Jul 2022
- 3 Minutes to read
ProGet Installation Guide
- Updated on 11 Jul 2022
- 3 Minutes to read
ProGet is self-managed, which means you have the option to run ProGet on-premise or in your private/public cloud. Both Windows and Linux are supported.
Installing on Windows Servers
ProGet doesn't have any intense server requirements, and supports all modern version of Windows that Microsoft supports (see Windows Lifecycle Fact Sheet).
The recommended Windows server requirements are:
- Minimum - 2 Core CPU, 2 GB RAM, 1 GB for storage
- Recommended Average/Typical - 2 Core CPU, 4 GB RAM, 10 GB storage
- Recommended Large - 4 Core CPU, 8 GB RAM, 16 GB Storage
There are two supported options; there is also Legacy (Traditional) Installer available for ProGet v5.3 and earlier.
Easiest: Inedo Hub
The easiest way to install ProGet on your Windows Servers is with Inedo Hub, which is a lightweight Windows application. The Inedo Hub is used to install, update, and otherwise service your ProGet installation, as well as other Inedo products installed on your server.
Install ProGet using the Inedo Hub
The Inedo Hub also supports Offline Installation for severs with limited or no Internet access.
Silent Installation for Automation
You can also perform a silent (non-interactive) installation of ProGet using the Inedo Hub. This won't display a user interface or ask any questions. This can be useful for scripts or other automations.
See: Silent/Automated Installation Guide
Fully Customizable: Manual Installation
We do not support manual installations, and this document is for informational and troubleshooting purposes only. If you really want to install the product without using Inedo Hub, you can follow these instructions to do so — but your successor may have a very difficult time maintainng this installation.
If you prefer to install every component of ProGet yourself, that's also an option.
See: Manual installation
Installing on Linux Servers
ProGet can run on a Linux server through Docker. We may support additional installation options in the future if there's any interest.
The recommended Container resources are:
- Minimum - 2 vCPU, 2 GB RAM
- Recommended Average/Typical - 2 vCPU, 4 GB RAM
- Recommended Large - v4 CPU, 8 GB RAM
In addition, we recommend reserving a volume with at least 10GB to store your packages and container images.
Install ProGet on Linux using Docker
In addition to Docker Engine, you can run ProGet through Docker Compose or Kubernetes.
Running in the Cloud
ProGet can be installed on a virtual machine or container in the cloud provider of your choosing.
See: Installing ProGet on AWS Lightsail.
Firewall & Network Access
On Windows, ProGet installs on port 8624 by default, and you should consider changing that after installation to the standard ports of HTTP (80) and/or HTTPS (443) after installation.
Whatever port you decide to access ProGet's web application on, you'll need to configure an Inbound Firewall rule to allow that access. No other inbound ports are required.
Outbound Network Access
ProGet doesn't require internet access. However, because ProGet is often used as a proxy to external repositories like nuget.org, dockerhub.io, etc., outbound network access on web ports (80, 443) is required if you want to use that feature.
Maintaining your ProGet Installation
Once your ProGet instance is up and running, there isn't a whole lot that you will need to manage or maintain.
Update ProGet at least quarterly; we ship a maintenance release of ProGet at least twice a month with bugfixes and low-risk changes. However, lots of small, low-risk changes add up over time, so we recommend updating at least once per quarter to minimize the risk of a regression.
Routinely back-up your instance to mitigate the risk of sudden hardware/server problems, as well as to make rolling back to previous versions of ProGet easy.
Configure Automatic Retention Rules so that unused packages and container images are automatically cleaned-up