mirror
/
docker-documentation
kopia lustrzana https://github.com/linuxserver/docker-documentation
1
0
Forkuj 0
Kod Zgłoszenia Packages Projekty Wydania Wiki Aktywność

Merge pull request #43 from linuxserver/broken-img

pull/45/head
Roxedus 2021-10-10 20:59:23 +02:00 zatwierdzone przez GitHub
rodzic 5f4b504a46 7a5bdc3e38
commit 5b67fc0e4a
Nie znaleziono w bazie danych klucza dla tego podpisu
ID klucza GPG: 4AEE18F83AFDEB23
1 zmienionych plików z 3 dodań i 3 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

6
general/swag.md
Wyświetl plik

@ -494,7 +494,7 @@ server {
A reverse proxy is a type of proxy server that retrieves resources on behalf of a client from one or more servers. These resources are then returned to the client as if they originated from the Web server itself (Shamelessly borrowed from [another post on our blog](https://blog.linuxserver.io/2017/11/28/how-to-setup-a-reverse-proxy-with-letsencrypt-ssl-for-all-your-docker-apps/#whatisareverseproxy)).
![reverseproxy](https://blog.linuxserver.io/content/images/2019/04/reverseproxy.png)
![reverseproxy](https://www.linuxserver.io/user/pages/content/images/2019/04/reverseproxy.png)
In this case, a user or a client browser can connect to our SWAG container via https on port 443, request a service such as Ombi, then our SWAG container connects to the ombi container, retrieves the data and passes it on to the client via https with our trusted cert. The connection to ombi is local and does not need to be encrypted, but all communication between our SWAG container and the client browser will be encrypted.
@ -934,11 +934,11 @@ Now we find the file named `nextcloud.subdomain.conf.sample` under SWAG's `/conf
If this is the first time we are accessing Nextcloud (we've never accessed it locally before), we can simply navigate to `https://nextcloud.linuxserver-test.duckdns.org` and we should see the Nextcloud set up page. We'll fill out the info, use the mariadb user `ncuser` and the password we selected in the environment variable (`ncpassword` in the above example) and we'll use `mariadb` as the Database Host address (container name as dns hostname).
![Screenshot-2019-04-14-at-18.35.02---Edited](https://blog.linuxserver.io/content/images/2019/04/Screenshot-2019-04-14-at-18.35.02---Edited.png)
![Screenshot-2019-04-14-at-18.35.02---Edited](https://www.linuxserver.io/user/pages/content/images/2019/04/Screenshot-2019-04-14-at-18.35.02---Edited.png)
We should then be able to go through the intro slides and then see the Nextcloud dashboard with our shiny padlock icon next to the address bar.
![Screenshot-2019-04-14-at-18.40.45---Edited](https://blog.linuxserver.io/content/images/2019/04/Screenshot-2019-04-14-at-18.40.45---Edited.png)
![Screenshot-2019-04-14-at-18.40.45---Edited](https://www.linuxserver.io/user/pages/content/images/2019/04/Screenshot-2019-04-14-at-18.40.45---Edited.png)
If this is an existing Nextcloud instance, or we set it up locally via the host IP address and local port, Nextcloud will reject proxied connections. In that case, we have to follow the instructions at the top of the `nextcloud.subdomain.conf` file: