added missing gogs third-party site
Dieser Commit ist enthalten in:
Ursprung
ec1cd07316
Commit
f38c49cdd5
2 geänderte Dateien mit 105 neuen und 0 gelöschten Zeilen
53
docs/third_party/third_party-gogs.de.md
gevendort
Normale Datei
53
docs/third_party/third_party-gogs.de.md
gevendort
Normale Datei
|
@ -0,0 +1,53 @@
|
||||||
|
Mit Gogs' Fähigkeit, sich über SMTP zu authentifizieren, ist es einfach, es mit mailcow zu verbinden. Es sind nur wenige Änderungen erforderlich:
|
||||||
|
|
||||||
|
1\. Ă–ffne `docker-compose.override.yml` und fĂĽge Gogs hinzu:
|
||||||
|
|
||||||
|
```
|
||||||
|
version: '2.1'
|
||||||
|
services:
|
||||||
|
|
||||||
|
gogs-mailcow:
|
||||||
|
image: gogs/gogs
|
||||||
|
volumes:
|
||||||
|
- ./data/gogs:/data
|
||||||
|
networks:
|
||||||
|
mailcow-network:
|
||||||
|
aliases:
|
||||||
|
- gogs
|
||||||
|
ports:
|
||||||
|
- "${GOGS_SSH_PORT:-127.0.0.1:4000}:22"
|
||||||
|
```
|
||||||
|
|
||||||
|
2\. Erstelle `data/conf/nginx/site.gogs.custom`, fĂĽge hinzu:
|
||||||
|
```
|
||||||
|
location /gogs/ {
|
||||||
|
proxy_pass http://gogs:3000/;
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
3\. Ă–ffne `mailcow.conf` und definiere die Bindung, die Gogs fĂĽr SSH verwenden soll. Beispiel:
|
||||||
|
|
||||||
|
```
|
||||||
|
GOGS_SSH_PORT=127.0.0.1:4000
|
||||||
|
```
|
||||||
|
|
||||||
|
5\. FĂĽhren Sie `docker-compose up -d` aus, um den Gogs-Container hochzufahren und fĂĽhren Sie anschlieĂźend `docker-compose restart nginx-mailcow` aus.
|
||||||
|
|
||||||
|
6\. Ă–ffnen Sie `http://${MAILCOW_HOSTNAME}/gogs/`, zum Beispiel `http://mx.example.org/gogs/`. FĂĽr Datenbank-Details setzen Sie `mysql` als Datenbank-Host. Verwenden Sie den in mailcow.conf gefundenen Wert von DBNAME als Datenbankname, DBUSER als Datenbankbenutzer und DBPASS als Datenbankpasswort.
|
||||||
|
|
||||||
|
7\. Sobald die Installation abgeschlossen ist, loggen Sie sich als Administrator ein und setzen Sie "Einstellungen" -> "Autorisierung" -> "SMTP aktivieren". SMTP-Host sollte `postfix` mit Port `587` sein, setzen Sie `Skip TLS Verify`, da wir ein nicht gelistetes SAN verwenden ("postfix" ist höchstwahrscheinlich nicht Teil Ihres Zertifikats).
|
||||||
|
|
||||||
|
8\. Erstellen Sie `data/gogs/gogs/conf/app.ini` und setzen Sie die folgenden Werte. Sie können [Gogs cheat sheet](https://gogs.io/docs/advanced/configuration_cheat_sheet) für ihre Bedeutung und andere mögliche Werte konsultieren.
|
||||||
|
|
||||||
|
```
|
||||||
|
[server]
|
||||||
|
SSH_LISTEN_PORT = 22
|
||||||
|
# FĂĽr GOGS_SSH_PORT=127.0.0.1:4000 in mailcow.conf, setzen:
|
||||||
|
SSH_DOMAIN = 127.0.0.1
|
||||||
|
SSH_PORT = 4000
|
||||||
|
# FĂĽr MAILCOW_HOSTNAME=mx.example.org in mailcow.conf (und Standard-Ports fĂĽr HTTPS), setzen:
|
||||||
|
ROOT_URL = https://mx.example.org/gogs/
|
||||||
|
```
|
||||||
|
|
||||||
|
9\. Starten Sie Gogs neu mit `docker-compose restart gogs-mailcow`. Ihre Benutzer sollten in der Lage sein, sich mit von mailcow verwalteten Konten einzuloggen.
|
||||||
|
|
52
docs/third_party/third_party-gogs.en.md
gevendort
Normale Datei
52
docs/third_party/third_party-gogs.en.md
gevendort
Normale Datei
|
@ -0,0 +1,52 @@
|
||||||
|
With Gogs' ability to authenticate over SMTP it is trivial to integrate it with mailcow. Few changes are needed:
|
||||||
|
|
||||||
|
1\. Open `docker-compose.override.yml` and add Gogs:
|
||||||
|
|
||||||
|
```
|
||||||
|
version: '2.1'
|
||||||
|
services:
|
||||||
|
|
||||||
|
gogs-mailcow:
|
||||||
|
image: gogs/gogs
|
||||||
|
volumes:
|
||||||
|
- ./data/gogs:/data
|
||||||
|
networks:
|
||||||
|
mailcow-network:
|
||||||
|
aliases:
|
||||||
|
- gogs
|
||||||
|
ports:
|
||||||
|
- "${GOGS_SSH_PORT:-127.0.0.1:4000}:22"
|
||||||
|
```
|
||||||
|
|
||||||
|
2\. Create `data/conf/nginx/site.gogs.custom`, add:
|
||||||
|
```
|
||||||
|
location /gogs/ {
|
||||||
|
proxy_pass http://gogs:3000/;
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
3\. Open `mailcow.conf` and define the binding you want Gogs to use for SSH. Example:
|
||||||
|
|
||||||
|
```
|
||||||
|
GOGS_SSH_PORT=127.0.0.1:4000
|
||||||
|
```
|
||||||
|
|
||||||
|
5\. Run `docker-compose up -d` to bring up the Gogs container and run `docker-compose restart nginx-mailcow` afterwards.
|
||||||
|
|
||||||
|
6\. Open `http://${MAILCOW_HOSTNAME}/gogs/`, for example `http://mx.example.org/gogs/`. 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.
|
||||||
|
|
||||||
|
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).
|
||||||
|
|
||||||
|
8\. Create `data/gogs/gogs/conf/app.ini` and set following values. You can consult [Gogs cheat sheet](https://gogs.io/docs/advanced/configuration_cheat_sheet) for their meaning and other possible values.
|
||||||
|
|
||||||
|
```
|
||||||
|
[server]
|
||||||
|
SSH_LISTEN_PORT = 22
|
||||||
|
# For GOGS_SSH_PORT=127.0.0.1:4000 in mailcow.conf, set:
|
||||||
|
SSH_DOMAIN = 127.0.0.1
|
||||||
|
SSH_PORT = 4000
|
||||||
|
# For MAILCOW_HOSTNAME=mx.example.org in mailcow.conf (and default ports for HTTPS), set:
|
||||||
|
ROOT_URL = https://mx.example.org/gogs/
|
||||||
|
```
|
||||||
|
|
||||||
|
9\. Restart Gogs with `docker-compose restart gogs-mailcow`. Your users should be able to login with mailcow managed accounts.
|
Laden …
In neuem Issue referenzieren