caaee7a124
* Add back changes from prior to purge * Manually fix some invalid Liquid * Updoot render-content * Improve test messages to show correct output * Run el scripto * Pass the remaining test
1.9 KiB
title, intro, redirect_from, versions
| title | intro | redirect_from | versions | |||
|---|---|---|---|---|---|---|
| Enabling GitHub Packages for your enterprise | You can start using {% data variables.product.prodname_registry %} on your instance by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate. |
|
|
{% data reusables.package_registry.packages-ghes-release-stage %}
-
After you've been invited to join the beta, to enable {% data variables.product.prodname_registry %} for your instance, follow the instructions from your account representative.
-
Configure third-party storage for your enterprise's packages. For more information, see "Configuring third-party storage for packages."
-
Enable or disable each package ecosystem for your enterprise. For more information, see "Configuring packages support for your enterprise."
-
If subdomain isolation is enabled for your instance, which is required to use {% data variables.product.prodname_registry %} 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 includeshttps://.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 {% data variables.product.prodname_registry %}. For more information about package host URLs, see "Enabling subdomain isolation." For more information about uploading TLS certificates to {% data variables.product.product_name %}, see "Configuring TLS."