Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update instructions for Studio Self-hosted CAs #4710

Merged
merged 2 commits into from
Jul 20, 2023
Merged

Update instructions for Studio Self-hosted CAs #4710

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
221e6d6
Update instructions for Studio Self-hosted CAs
Jul 20, 2023
7181491
Fix linting
Jul 20, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 15 additions & 9 deletions content/docs/studio/self-hosting/configuration/ca.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,16 +1,22 @@
# CA certificates

Does your Git forge use a certificate signed by a custom certificate authority
(CA)? If so, Studio needs to have the CA certificate in order to connect to the
Git forge.
Do you use a custom certificate for Studio or one of your Git forges? If so,
Studio needs to have the CA certificates in order to establish connections.

To do this, copy your CA certificate as plain text, then insert it in the
`customCaCert` key in the `values.yaml` configuration file:
To do this, copy your CA certificates as plain text, then add them to the
`customCaCerts` list in the `values.yaml` configuration file:

```yaml
global:
customCaCert: |-
-----BEGIN CERTIFICATE-----
....
-----END CERTIFICATE-----
customCaCerts:
# First certificate
- |-
-----BEGIN CERTIFICATE-----
....
-----END CERTIFICATE-----
# Second certificate
- |-
-----BEGIN CERTIFICATE-----
....
-----END CERTIFICATE-----
```
Loading