jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-25 02:17:36 -05:00
Code Issues Projects Releases Wiki Activity

Swap product_name for prodname_ghe_server in GHES docs (#54031)

Browse Source 
Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com>
Co-authored-by: Sarah Schneider <sarahs@users.noreply.github.com>
Co-authored-by: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com>
This commit is contained in:
Isaac Brown
2025-01-22 17:37:52 +00:00
committed by GitHub
parent 87739ebd92
commit 5a2ca78e45
56 changed files with 138 additions and 138 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/admin/configuring-packages/getting-started-with-github-packages-for-your-enterprise.md
View File

@@ -63,7 +63,7 @@ Choose which package ecosystems you'd like to enable, disable, or set to read-on
If subdomain isolation is enabled for {% data variables.location.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 `{% data reusables.package_registry.container-registry-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 [AUTOTITLE](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation). For more information about uploading TLS certificates to {% data variables.product.product_name %}, see [AUTOTITLE](/admin/configuration/configuring-network-settings/configuring-tls).
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 [AUTOTITLE](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation). For more information about uploading TLS certificates to {% data variables.product.prodname_ghe_server %}, see [AUTOTITLE](/admin/configuration/configuring-network-settings/configuring-tls).
## Step 6: Check for and rename reserved names

8
content/admin/configuring-packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md
View File

@@ -36,7 +36,7 @@ For more information about configuring {% data variables.product.prodname_regist
## Migrating organizations to the {% data variables.product.prodname_container_registry %}
You can start a migration of all your organizations' Docker images to the {% data variables.product.prodname_container_registry %}. The duration of the migration operation depends on the total number of images to migrate, and the overall load on your instance. After a successful migration, {% data variables.product.product_name %} will display a summary, and all future uploads of Docker images will use the {% data variables.product.prodname_container_registry %}.
You can start a migration of all your organizations' Docker images to the {% data variables.product.prodname_container_registry %}. The duration of the migration operation depends on the total number of images to migrate, and the overall load on your instance. After a successful migration, {% data variables.product.prodname_ghe_server %} will display a summary, and all future uploads of Docker images will use the {% data variables.product.prodname_container_registry %}.
If a site administrator has configured email notifications for {% data variables.location.product_location %}, you will receive an email after the migration is complete. For more information, see [AUTOTITLE](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications).
@@ -48,7 +48,7 @@ During the migration, the CPU and memory usage for your instance will increase.
### After the migration
After the migration, storage pressure on your instance will increase due to the duplication of image files in the Docker registry and the {% data variables.product.prodname_container_registry %}. A future release of {% data variables.product.product_name %} will remove the duplicated files when all migrations are complete.
After the migration, storage pressure on your instance will increase due to the duplication of image files in the Docker registry and the {% data variables.product.prodname_container_registry %}. A future release of {% data variables.product.prodname_ghe_server %} will remove the duplicated files when all migrations are complete.
For more information about monitoring the performance and storage of {% data variables.location.product_location %}, see [AUTOTITLE](/admin/monitoring-and-managing-your-instance/monitoring-your-instance/about-the-monitor-dashboards).
@@ -57,7 +57,7 @@ For more information about monitoring the performance and storage of {% data var
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.settings-tab %}
1. In the left sidebar, click **Packages**.
1. To the right of the number of packages to migrate, click **Start migration**. During the migration, {% data variables.product.product_name %} will display progress on this page.
1. To the right of the number of packages to migrate, click **Start migration**. During the migration, {% data variables.product.prodname_ghe_server %} will display progress on this page.
After the migration completes, the page will display the results. If a migration fails, the page will show the organizations that own the package that caused the failure.
@@ -69,5 +69,5 @@ Prior to migration, if a user has created a package in the {% data variables.pro
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.settings-tab %}
{% data reusables.enterprise-accounts.packages-tab %}
1. To the right of the number of packages to migrate, click **Re-run migration**. During the migration, {% data variables.product.product_name %} will display progress on this page.
1. To the right of the number of packages to migrate, click **Re-run migration**. During the migration, {% data variables.product.prodname_ghe_server %} will display progress on this page.
1. If the migration fails again, start from step 1 and re-run the migration.