Update third_party-gitea.md
Added a step needed if you use http to https redirect
Dieser Commit ist enthalten in:
Ursprung
3022fd3320
Commit
b2e3599d0b
1 geänderte Dateien mit 6 neuen und 4 gelöschten Zeilen
|
@ -33,11 +33,13 @@ GITEA_SSH_PORT=127.0.0.1:4000
|
||||||
|
|
||||||
5\. Run `docker-compose up -d` to bring up the gitea container and run `docker-compose restart nginx-mailcow` afterwards.
|
5\. Run `docker-compose up -d` to bring up the gitea container and run `docker-compose restart nginx-mailcow` afterwards.
|
||||||
|
|
||||||
6\. Open `http://${MAILCOW_HOSTNAME}/gitea/`, for example `http://mx.example.org/gitea/`. For database details set `mysql` as database host. Use the value of DBNAME found in mailcow.conf as database name, DBUSER as database user and DBPASS as database password.
|
6\. If you forced mailcow to https, execute step 9 and restart gitea with `docker-compose restart gitea-mailcow` . Go head with step 7 (Remember to use https instead of http, `https://mx.example.org/gitea/`
|
||||||
|
|
||||||
7\. Once the installation is complete, login as admin and set "settings" -> "authorization" -> "enable SMTP". SMTP Host should be `postfix` with port `587`, set `Skip TLS Verify` as we are using an unlisted SAN ("postfix" is most likely not part of your certificate).
|
7\. Open `http://${MAILCOW_HOSTNAME}/gitea/`, for example `http://mx.example.org/gitea/`. For database details set `mysql` as database host. Use the value of DBNAME found in mailcow.conf as database name, DBUSER as database user and DBPASS as database password.
|
||||||
|
|
||||||
8\. Create `data/gitea/gitea/conf/app.ini` and set following values. You can consult [gitea cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/) for their meaning and other possible values.
|
8\. Once the installation is complete, login as admin and set "settings" -> "authorization" -> "enable SMTP". SMTP Host should be `postfix` with port `587`, set `Skip TLS Verify` as we are using an unlisted SAN ("postfix" is most likely not part of your certificate).
|
||||||
|
|
||||||
|
9\. Create `data/gitea/gitea/conf/app.ini` and set following values. You can consult [gitea cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/) for their meaning and other possible values.
|
||||||
|
|
||||||
```
|
```
|
||||||
[server]
|
[server]
|
||||||
|
@ -49,4 +51,4 @@ SSH_PORT = 4000
|
||||||
ROOT_URL = https://mx.example.org/gitea/
|
ROOT_URL = https://mx.example.org/gitea/
|
||||||
```
|
```
|
||||||
|
|
||||||
9\. Restart gitea with `docker-compose restart gitea-mailcow`. Your users should be able to login with mailcow managed accounts.
|
10\. Restart gitea with `docker-compose restart gitea-mailcow`. Your users should be able to login with mailcow managed accounts.
|
||||||
|
|
Laden …
In neuem Issue referenzieren