Installing and Managing ProGet

ProGet can be deployed on Windows, Linux, or in High Availability (HA) environments using a consistent management model across platforms.

Unlike Sonatype environments that separate functionality across multiple products and interfaces, ProGet centralizes package management, governance, and administration within a single platform.

This chapter covers:

• single-server installations
• High Availability deployments
• instance upgrade and maintenance workflows

Single-Server Installation

For most migrations, ProGet can be deployed using hardware specifications similar to the existing Sonatype environment. Resource usage can then be adjusted based on package volume, retention policies, and scanning requirements.

Windows Installation

On Windows, ProGet is typically installed and managed through Inedo Hub. Inedo Hub provides:

• installation and configuration workflows
• service management
• upgrade and rollback support
• instance monitoring and maintenance

After installation, the onboarding wizard guides the initial configuration process.

Linux and Docker Installation

On Linux, ProGet can be deployed using Docker container images.

Scripted and silent installation options are also available for automated provisioning workflows.

Once deployed, the onboarding wizard is used to complete initial configuration.

👉🏻 See the ProGet documentation for installation guides, deployment examples, and configuration walkthroughs.

High Availability Deployments

ProGet supports High Availability (HA) deployments for environments that require increased redundancy, scalability, and uptime.

HA deployments use the same core installation process as single-server deployments while adding shared infrastructure components.

Typical HA environments include:

• load balancers
• shared storage
• shared databases
• shared encryption keys and configuration settings

These components allow multiple ProGet nodes to operate together as a single coordinated environment.

Maintaining Your ProGet Instance

Upgrades and Updates

On Windows, upgrades are managed through Inedo Hub. Upgrade workflows preserve existing packages and configuration data while reducing operational disruption.

On Linux and Docker deployments, upgrades are typically performed using deployment scripts or container update workflows.

Rollback and Downgrade Support

ProGet also supports rollback and downgrade workflows when needed.

Unlike manual migration or export/import approaches often required in other repository platforms, ProGet preserves package data and configuration state during version transitions, reducing administrative complexity.

Operational Management

ProGet uses a centralized management model across both single-server and High Availability deployments.

Instead of separating package management, governance, and administration across multiple tools, ProGet manages these capabilities within a single platform. Installation and maintenance workflows are supported through Inedo Hub on Windows and Docker-based deployments on Linux.

The same operational model applies across environments, helping standardize administration as infrastructure scales.

This model extends into how repositories are structured and managed. The next article covers Feeds and Package Repositories, including feed configuration, repository behavior, and Connector-based integration with external and internal sources.