3b092b4cb8
* Update enterprise-server-releases.js * Run deprecation script * Remove finding / managing security vulnerabilities * remove vuln from translations * remove more dead pages * Restore heavily used files * Remove 2.22 refs in tests * Update working-with-the-npm-registry.md
3.1 KiB
title, shortTitle, intro, redirect_from, versions, type, topics
| title | shortTitle | intro | redirect_from | versions | type | topics | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Getting started with GitHub Packages for your enterprise | Getting started with GitHub Packages | You can start using {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate. |
|
|
how_to |
|
{% data reusables.package_registry.packages-cluster-support %}
Step 1: Enable {% data variables.product.prodname_registry %} and configure external storage
{% data variables.product.prodname_registry %} on {% data variables.product.prodname_ghe_server %} uses external blob storage to store your packages.
After enabling {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, you'll need to prepare your third-party storage bucket. The amount of storage required depends on your usage of {% data variables.product.prodname_registry %}, and the setup guidelines can vary by storage provider.
Supported external storage providers
- Amazon Web Services (AWS) S3 {% ifversion ghes %}
- Azure Blob Storage {% endif %}
- MinIO
To enable {% data variables.product.prodname_registry %} and configure third-party storage, see:
- "Enabling GitHub Packages with AWS"{% ifversion ghes %}
- "Enabling GitHub Packages with Azure Blob Storage"{% endif %}
- "Enabling GitHub Packages with MinIO"
Step 2: Specify the package ecosystems to support on your instance
Choose which package ecosystems you'd like to enable, disable, or set to read-only on {% data variables.product.product_location %}. Available options are Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. For more information, see "Configuring package ecosystem support for your enterprise."
Step 3: Ensure you have a TLS certificate for your package host URL, if needed
If subdomain isolation is enabled for {% data variables.product.product_location %}, you will need to 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 you can use 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."