diff options
| author | Freeroot <free.r@gmx.fr> | 2018-05-11 12:46:39 +0200 |
|---|---|---|
| committer | Freeroot <free.r@gmx.fr> | 2018-05-11 12:46:39 +0200 |
| commit | 64a531b42821a4ba4557292e2898b611174a86bf (patch) | |
| tree | 9c1f6fb075d82cb038b69c2d0568205a00695269 /.examples | |
| parent | 7f611a569e38cc79957407fe6383b095141ae128 (diff) | |
add infos from #409 in doc
Diffstat (limited to '.examples')
| -rw-r--r-- | .examples/README.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/.examples/README.md b/.examples/README.md index cc1dae73..45065bbb 100644 --- a/.examples/README.md +++ b/.examples/README.md @@ -94,7 +94,9 @@ If you want to update your installation to a newer version of nextcloud, repeat The nginx proxy adds a proxy layer between nextcloud and the internet. The proxy is designed to serve multiple sites on the same host machine. The advantage in adding this layer is the ability to add a container for [Let's Encrypt](https://letsencrypt.org/) certificate handling. -This combination of the [jwilder/nginx-proxy](https://github.com/jwilder/nginx-proxy) and [jrcs/docker-letsencrypt-nginx-proxy-companion](https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion) containers creates a fully automated https encryption of the nextcloud installation without worrying about certificate generation, validation or renewal (needs a domain name and not for local setup). +This combination of the [jwilder/nginx-proxy](https://github.com/jwilder/nginx-proxy) and [jrcs/docker-letsencrypt-nginx-proxy-companion](https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion) containers creates a fully automated https encryption of the nextcloud installation without worrying about certificate generation, validation or renewal. + +**This setup only works with a valid domain name on a server that is reachable from the internet.** To use this example complete the following steps: |