Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
c01f99b7
G
gitlab-foss
项目概览
李少辉-开发者
/
gitlab-foss
通知
15
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
gitlab-foss
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
c01f99b7
编写于
5月 22, 2016
作者:
A
Achilleas Pipinellis
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Fixes suggested by Kamil
上级
f896a4e0
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
9 addition
and
23 deletion
+9
-23
doc/administration/container_registry.md
doc/administration/container_registry.md
+9
-23
未找到文件。
doc/administration/container_registry.md
浏览文件 @
c01f99b7
...
...
@@ -31,15 +31,9 @@ You can read more about Docker Registry at https://docs.docker.com/registry/intr
**Omnibus GitLab installations**
1.
Open
`/etc/gitlab/gitlab.rb`
and edit or add the following line:
```ruby
gitlab_rails['registry_enabled'] = true
```
1.
The next step is to configure the domain name under which the Container
Registry will listen to. Read
[
#container-registry-domain-configuration
](
#container-registry-domain-configuration
)
and pick one of the two options that fits your case.
All you have to do is configure the domain name under which the Container
Registry will listen to. Read
[
#container-registry-domain-configuration
](
#container-registry-domain-configuration
)
and pick one of the two options that fits your case.
>**Note:**
The container Registry works under HTTPS by default. Using HTTP is possible
...
...
@@ -124,15 +118,11 @@ GitLab from source respectively.
path to the existing TLS certificate and key used by GitLab:
```ruby
gitlab_rails['registry_host'] = "gitlab.example.com"
gitlab_rails['registry_port'] = "4567"
# The following setting is needed for NGINX
registry_external_url 'https://gitlab.example.com:4567'
```
Note how the `registry_external_url` is listening on HTTPS
and is a
conjunction of `registry_host` and `registry_port`
.
Note how the `registry_external_url` is listening on HTTPS
under the
existing GitLab URL, but on a different port
.
If your TLS certificate is not in `/etc/gitlab/ssl/gitlab.example.com.crt`
and key not in `/etc/gitlab/ssl/gitlab.example.com.key` uncomment the lines
...
...
@@ -197,12 +187,11 @@ Let's assume that you want the container Registry to be accessible at
1.
Once the TLS certificate is in place, edit
`/etc/gitlab/gitlab.rb`
with:
```ruby
gitlab_rails['registry_host'] = "registry.gitlab.example.com"
# The following setting is needed for NGINX
registry_external_url 'https://registry.gitlab.example.com'
```
Note how the `registry_external_url` is listening on HTTPS.
1.
Save the file and
[
reconfigure GitLab
][]
for the changes to take effect.
> **Note:**
...
...
@@ -249,12 +238,10 @@ Registry application itself.
**Omnibus GitLab**
1.
Open
`/etc/gitlab/gitlab.rb`
and set
`gitlab_rails['registry_enabled']`
to
`false`
and comment out the
`registry_external_url`
:
1.
Open
`/etc/gitlab/gitlab.rb`
and set
`registry['enable']`
to
`false`
:
```ruby
gitlab_rails['registry_enabled'] = false
# registry_external_url 'https://registry.gitlab.example.com'
registry['enable'] = false
```
1.
Save the file and
[
reconfigure GitLab
][]
for the changes to take effect.
...
...
@@ -326,7 +313,6 @@ This path is accessible to:
-
the user running the Container Registry daemon,
-
the user running GitLab
-
and to the user running the Nginx web server.
> **Warning** You should confirm that all GitLab, Registry and web server users
have access to this directory.
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录