Enabling GitHub Packages for your enterprise

You can start using GitHub Packages on your instance by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate.

Did this doc help you?

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.

Note: GitHub Packages is currently in beta for GitHub Enterprise Server 2.22. To join the beta for your instance, use the sign-up form.

  1. After you've been invited to join the beta, to enable GitHub Packages for your instance, follow the instructions from your account representative.

  2. Configure third-party storage for your enterprise's packages. For more information, see "Configuring third-party storage for packages."

  3. Enable or disable each package ecosystem for your enterprise. For more information, see "Configuring packages support for your enterprise."

  4. If subdomain isolation is enabled for your instance, which is required to use GitHub Packages with Docker, create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as npm.HOSTNAME. Make sure each package host URL includes https://.

    You can create the certificate manually or using Let's Encrypt. If you already use Let's Encrypt, you must request a new TLS certificate after enabling GitHub Packages. For more information about package host URLs, see "Enabling subdomain isolation." For more information about uploading TLS certificates to GitHub Enterprise, see "Configuring TLS."

Did this doc help you?

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.