@@ -14,7 +14,7 @@ The default functionality of Gitlab is limited at the project level. This can be
1414of
1515projects, potentially resulting in undetected failed pipelines.
1616
17- ## 👉 [ Demo (main branch) ] ( https://gitlab-ci-dashboard.larscom.nl )
17+ ## 👉 [ Demo] ( https://gitlab-ci-dashboard.larscom.nl )
1818
1919<br />
2020
@@ -66,13 +66,22 @@ projects, potentially resulting in undetected failed pipelines.
66662 . Run docker with the required environment variables (GITLAB_BASE_URL, GITLAB_API_TOKEN)
6767
6868``` bash
69- docker run -p 8080:8080 -e GITLAB_BASE_URL=https://gitlab.com -e GITLAB_API_TOKEN=my_token larscom/gitlab-ci-dashboard:latest
69+ docker run \
70+ -p 8080:8080 \
71+ -e GITLAB_BASE_URL=https://gitlab.com \
72+ -e GITLAB_API_TOKEN=my_token \
73+ larscom/gitlab-ci-dashboard:latest
7074```
7175
7276Or you can run it with a TOML configration file
7377
7478``` bash
75- docker run -p 8080:8080 -v $( pwd) /config.toml:/app/config.toml larscom/gitlab-ci-dashboard:latest
79+ docker run \
80+ -p 8080:8080 \
81+ -e GITLAB_BASE_URL=https://gitlab.com \
82+ -e GITLAB_API_TOKEN=my_token \
83+ -v ./config.toml:/app/config.toml \
84+ larscom/gitlab-ci-dashboard:latest
7685```
7786
78873 . Dashboard should be available at: http://localhost:8080/ showing (by default) all available groups and their
@@ -103,13 +112,39 @@ A TOML file takes precedence over environment variables, except for the `RUST_LO
103112
104113> An example TOML file can be found inside the ` ./api ` folder.
105114
106- Mount the ` config.toml ` inside the container.
115+ Mount the ` config.toml ` inside the container ( ` /app/config.toml ` )
107116
108117``` bash
109- docker run -p 8080:8080 -v $( pwd) /config.toml:/app/config.toml larscom/gitlab-ci-dashboard:latest
118+ docker run \
119+ -p 8080:8080 \
120+ -e GITLAB_BASE_URL=https://gitlab.com \
121+ -e GITLAB_API_TOKEN=my_token \
122+ -v ./config.toml:/app/config.toml \
123+ larscom/gitlab-ci-dashboard:latest
110124```
111125
112- ### Environment variables
126+ ## 📜 Custom CA certificate
127+ If you are running a gitlab instance that is using a TLS certificate signed with a private CA you are able to provide that CA as mount (PEM encoded)
128+
129+ This is needed when the dashboard backend is unable to make a connection to the gitlab API over HTTPS.
130+
131+ Mount the ` ca.crt ` inside the container (` /app/certs/ca.crt ` )
132+
133+ ``` bash
134+ docker run \
135+ -p 8080:8080 \
136+ -e GITLAB_BASE_URL=https://gitlab.com \
137+ -e GITLAB_API_TOKEN=my_token \
138+ -v ./ca.crt:/app/certs/ca.crt \
139+ larscom/gitlab-ci-dashboard:latest
140+ ```
141+
142+ ### Troubleshooting
143+ If you are still unable to connect with a custom CA cert, be sure that the gitlab server certificate contains a valid SAN (Subject Alternative Name)
144+
145+ If there is a mismatch the HTTP client is still unable to make a proper connection.
146+
147+ ## 🌍 Environment variables
113148
114149| Variable | Type | Description | Required | Default |
115150| -----------------------------------| --------| ------------------------------------------------------------------------------------------------------------------------------------| ----------| --------------|
0 commit comments