Skip to content

Commit e1925ea

Browse files
cdluminateStelios Malathouras
authored and
Stelios Malathouras
committed
[doc] https-setup: explain relative paths for {CERT,KEY}_FILE fields. (go-gitea#18244)
Closes: go-gitea#14401
1 parent 3b18b41 commit e1925ea

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

docs/content/doc/usage/https-support.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,8 @@ KEY_FILE = key.pem
4040
Note that if your certificate is signed by a third party certificate authority (i.e. not self-signed), then cert.pem should contain the certificate chain. The server certificate must be the first entry in cert.pem, followed by the intermediaries in order (if any). The root certificate does not have to be included because the connecting client must already have it in order to estalbish the trust relationship.
4141
To learn more about the config values, please checkout the [Config Cheat Sheet](../config-cheat-sheet#server-server).
4242

43+
For the `CERT_FILE` or `KEY_FILE` field, the file path is relative to the `GITEA_CUSTOM` environment variable when it is a relative path. It can be an absolute path as well.
44+
4345
### Setting up HTTP redirection
4446

4547
The Gitea server is only able to listen to one port; to redirect HTTP requests to the HTTPS port, you will need to enable the HTTP redirection service:

0 commit comments

Comments
 (0)