Warnings:
- It is critical that you set the restrictive access policies you need for your storage bucket, because GitHub does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible on the public internet. If restrictions by IP address have been set up, please include IP addresses for your GitHub Enterprise Server instance and the end users who will be using the your GitHub Enterprise Server instance.
- We recommend using a dedicated bucket for GitHub Packages, separate from the bucket you use for GitHub Actions storage.
- Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using GitHub Packages.
Before you can enable and configure GitHub Packages on your GitHub Enterprise Server instance, you need to prepare your Azure Blob storage bucket. To prepare your Azure Blob storage bucket, we recommend consulting the official Azure Blob storage docs at the official
Azure Blob Storage documentation site
.
-
From an administrative account on GitHub Enterprise Server, in the upper-right corner of any page, click
.
-
If you're not already on the "Site admin" page, in the upper-left corner, click
Site admin
.
-
In the "
Site admin" sidebar, click
Management Console
.
-
In the left sidebar, click
Packages
.
-
Under "GitHub Packages", select the
Enable GitHub Packages
checkbox.
-
Under "Packages Storage", select
Azure Blob Storage
and enter your Azure container name for your packages storage bucket and connection string.
You must create a storage container prior to setting the container name and connection string.
Note:
You can find your Azure Connection String by navigating to the Access Key menu in your Azure storage account.
Usage of a SAS Token or SAS URL as connection string is not currently supported.
-
Under the "Settings" sidebar, click
Save settings
.
Note:
Saving settings in the Management Console restarts system services, which could result in user-visible downtime.
-
Wait for the configuration run to complete.
As a next step, you can customize which package ecosystems you would like to make available to end users on your GitHub Enterprise Server instance. For more information, see "
Configuring package ecosystem support for your enterprise
."
For an overview of getting started with GitHub Packages on GitHub, see "
Getting started with GitHub Packages for your enterprise
."
