ProGet Documentation

Feeds in ProGet

A feed is a uniquely-named repository in ProGet that contains packages. Each feed in ProGet is its own isolated repository, and can have its own configuration and scoped security privileges.

Feed Type

The type of a feed defines the type of package that it will contain. A NuGet feed, for example, will only ever store NuGet packages, and an npm feed will only ever store npm packages.

Each feed type will have its own API and endpoint URL for native clients to connect to. Since package management systems vary, each feed type will generally also have its own rules about naming and versioning.

See the specific feed type documentation for more information about how ProGet implements certain types of feeds.

Feed Dashboard

The feed management page shows a small dashboard with all current feed configuration, and a few graphs showing largest packages and package cache usage. These can be useful for setting up retention policies.

Feed Settings

Most feed types share some common configuration settings:

  • Name - Uniquely identifies the feed within ProGet. It is strongly encouraged to keep this name URL-friendly to make configuration with third-party clients easier.
  • Description - User-provided text that is displayed within the ProGet software when browsing the feed.
  • Caching - Determines whether connector package caching is enabled.
  • Disk Path - Specifies the physical disk path where packages are stored (when using the default package store).
  • Package Store - Specifies the storage mechanism for packages. The default store uses a disk path; S3 and Azure stores are included as extensions.
  • Drop Path - A file system directory that ProGet will periodically scan for packages, and move them to the feed if they are valid.

Deleting a Feed

A feed can either be deactivated or deleted. Deactivating a feed will make it invisible from most of the user interface, and inaccessible from API endpoints.

Deleting a feed will remove it entirely from the software. All package data indexed in the database will be deleted, as well as metadata not stored in the package itself, such as publish dates and download counts for each package.

Packages themselves are not deleted when deleting a feed. If you would like to delete them, make note of the feed disk path and delete them manually after deleting the feed.

More on this topic: