diff options
Diffstat (limited to 'doc/administration/packages')
| -rw-r--r-- | doc/administration/packages/container_registry.md | 7 | ||||
| -rw-r--r-- | doc/administration/packages/dependency_proxy.md | 9 | ||||
| -rw-r--r-- | doc/administration/packages/index.md | 5 |
3 files changed, 12 insertions, 9 deletions
diff --git a/doc/administration/packages/container_registry.md b/doc/administration/packages/container_registry.md index d04e3217f57..2623f2afd8d 100644 --- a/doc/administration/packages/container_registry.md +++ b/doc/administration/packages/container_registry.md @@ -1,6 +1,6 @@ --- stage: Package -group: Package +group: Container Registry info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- @@ -198,7 +198,8 @@ docker login gitlab.example.com:5050 When the Registry is configured to use its own domain, you need a TLS certificate for that specific domain (for example, `registry.example.com`). You might need a wildcard certificate if hosted under a subdomain of your existing GitLab -domain, for example, `registry.gitlab.example.com`. +domain. For example, `*.gitlab.example.com`, is a wildcard that matches `registry.gitlab.example.com`, +and is distinct from `*.example.com`. As well as manually generated SSL certificates (explained here), certificates automatically generated by Let's Encrypt are also [supported in Omnibus installs](https://docs.gitlab.com/omnibus/settings/ssl.html). @@ -1156,7 +1157,7 @@ blobs start being deleted is anything permanent done. ## Configuring GitLab and Registry to run on separate nodes (Omnibus GitLab) By default, package assumes that both services are running on the same node. -In order to get GitLab and Registry to run on a separate nodes, separate configuration +To get GitLab and Registry to run on a separate nodes, separate configuration is necessary for Registry and GitLab. ### Configuring Registry diff --git a/doc/administration/packages/dependency_proxy.md b/doc/administration/packages/dependency_proxy.md index 789863e8ed0..f6eb6f85274 100644 --- a/doc/administration/packages/dependency_proxy.md +++ b/doc/administration/packages/dependency_proxy.md @@ -1,6 +1,6 @@ --- stage: Package -group: Package +group: Container Registry info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- @@ -215,11 +215,12 @@ For installations from source: RAILS_ENV=production sudo -u git -H bundle exec rake gitlab:dependency_proxy:migrate ``` -You can optionally track progress and verify that all packages migrated successfully using the +You can optionally track progress and verify that all Dependency Proxy blobs and manifests migrated successfully using the [PostgreSQL console](https://docs.gitlab.com/omnibus/settings/database.html#connecting-to-the-bundled-postgresql-database): -- For Omnibus GitLab instances: `sudo gitlab-rails dbconsole` -- For installations from source: `sudo -u git -H psql -d gitlabhq_production` +- `sudo gitlab-rails dbconsole` for Omnibus GitLab 14.1 and earlier. +- `sudo gitlab-rails dbconsole --database main` for Omnibus GitLab 14.2 and later. +- `sudo -u git -H psql -d gitlabhq_production` for source-installed instances. Verify that `objectstg` (where `file_store = '2'`) has the count of all Dependency Proxy blobs and manifests for each respective query: diff --git a/doc/administration/packages/index.md b/doc/administration/packages/index.md index a7ab0fb3246..74d835eb744 100644 --- a/doc/administration/packages/index.md +++ b/doc/administration/packages/index.md @@ -1,6 +1,6 @@ --- stage: Package -group: Package +group: Package Registry info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- @@ -231,7 +231,8 @@ RAILS_ENV=production sudo -u git -H bundle exec rake gitlab:packages:migrate You can optionally track progress and verify that all packages migrated successfully using the [PostgreSQL console](https://docs.gitlab.com/omnibus/settings/database.html#connecting-to-the-bundled-postgresql-database): -- `sudo gitlab-rails dbconsole` for Omnibus GitLab instances. +- `sudo gitlab-rails dbconsole` for Omnibus GitLab 14.1 and earlier. +- `sudo gitlab-rails dbconsole --database main` for Omnibus GitLab 14.2 and later. - `sudo -u git -H psql -d gitlabhq_production` for source-installed instances. Verify `objectstg` below (where `file_store = '2'`) has count of all packages: |