Merge pull request plone#1249 from valentinab25/6-dev

Docker install documentation review

Author: ericof

docs/install/containers/examples/haproxy-plone-zeo.md

@@ -0,0 +1,77 @@
+---
+html_meta:
+  "description": "Simple Plone 6 setup with scalable backend and data being persisted in a Zeo volume."
+  "property=og:description": "Simple Plone 6 setup with scalable backend and data being persisted in a Zeo volume."
+  "property=og:title": "HAproxy, Backend, ZEO container example"
+  "keywords": "Plone 6, Container, Docker, HAproxy, Zeo"
+---
+
+# Haproxy, Backend, ZEO container example
+
+Very simple setup with only one or more backend instances accessing a ZEO server and data being persisted in a Docker volume.
+
+HAProxy is used for load balancing in this example.
+
+## Setup
+
+Create a directory for your project, and inside it create a `docker-compose.yml` file that starts your Plone instance and the ZEO instance with volume mounts for data persistence.
+
+```yaml
+version: "3"
+services:
+
+  lb:
+    image: plone/plone-haproxy
+    depends_on:
+    - backend
+    ports:
+    - "8080:8080"
+    - "1936:1936"
+    environment:
+      FRONTEND_PORT: "8080"
+      BACKENDS: "backend"
+      BACKENDS_PORT: "8080"
+      DNS_ENABLED: "True"
+      HTTPCHK: "GET /"
+      INTER: "5s"
+      LOG_LEVEL: "info"
+
+  backend:
+    image: plone/plone-backend:6.0.0a4
+    restart: always
+    environment:
+      ZEO_ADDRESS: zeo:8100
+    ports:
+    - "8080"
+    depends_on:
+      - zeo
+
+  zeo:
+    image: plone/plone-zeo:latest
+    restart: always
+    volumes:
+      - data:/data
+    ports:
+    - "8100"
+
+volumes:
+  data: {}
+```
+
+## Build the project with multiple backends
+
+Run `docker-compose up -d --scale backend=4` from your project directory.
+
+## Access Plone via Browser
+
+Point your browser at `http://localhost:8080`, using the username and password combination of `admin` and `admin`, and you should see the default Plone site creation page.
+
+## Access HAProxy Stats Page via Browser
+
+Point your browser at `http://localhost:1936`, using the username and password combination of `admin` and `admin`, and you should see HAProxy statistics for your Plone cluster.
+
+## Shutdown and cleanup
+
+The command `docker-compose down` removes the containers and default network, but preserves the Plone database.
+
+The command `docker-compose down --volumes` removes the containers, default network, and the Plone database.

docs/install/containers/examples/index.md

@@ -16,6 +16,7 @@ nginx-volto-plone
 nginx-volto-plone-zeo
 nginx-volto-plone-postgresql
 nginx-plone
+haproxy-plone-zeo
 ```
 
 Examples of projects running Plone using `docker-compose`.
@@ -26,3 +27,4 @@ Examples of projects running Plone using `docker-compose`.
 | [nginx-volto-plone-zeo](nginx-volto-plone-zeo) | Stack with nginx, Frontend, Backend and ZEO server |
 | [nginx-volto-plone-postgresql](nginx-volto-plone-postgresql) | Stack with nginx, Frontend, Backend and PostgreSQL DB |
 | [nginx-plone](nginx-plone) | Stack with nginx, and Backend (Plone Classic) |
+| [haproxy-plone-zeo](haproxy-plone-zeo) | Stack with haproxy, Backend and ZEO server |

docs/install/containers/examples/nginx-plone.md

@@ -10,6 +10,8 @@ html_meta:
 
 Simple setup with one backend and data being persisted in a Docker volume.
 
+Nginx in this example is used as a [reverse proxy](https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/").
+
 
 ## Setup
 
@@ -50,6 +52,10 @@ server {
 }
 ```
 
+```{note}
+`http://plone.localhost/` is the url you will be using to access the website.
+You can either use `localhost`, or add it in your `etc/hosts` file or DNS to point to the docker host IP.
+```
 
 ### Service configuration with `docker-compose`
 

docs/install/containers/examples/nginx-volto-plone-postgresql.md

@@ -10,6 +10,8 @@ html_meta:
 
 Very simple setup with only one or more backend instances accessing a Postgres server and data being persisted in a Docker volume.
 
+Nginx in this example is used as a [reverse proxy](https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/").
+
 
 ## Setup
 
@@ -75,6 +77,10 @@ server {
 }
 ```
 
+```{note}
+`http://plone.localhost/` is the url you will be using to access the website.
+You can either use `localhost`, or add it in your `etc/hosts` file or DNS to point to the docker host IP.
+```
 
 ### Service configuration with `docker-compose`
 

docs/install/containers/examples/nginx-volto-plone-zeo.md

@@ -10,6 +10,7 @@ html_meta:
 
 Very simple setup with only one or more backend instances accessing a ZEO server and data being persisted in a Docker volume.
 
+Nginx in this example is used as a [reverse proxy](https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/").
 
 ## Setup
 
@@ -75,6 +76,10 @@ server {
 }
 ```
 
+```{note}
+`http://plone.localhost/` is the url you will be using to access the website.
+You can either use `localhost`, or add it in your `etc/hosts` file or DNS to point to the docker host IP.
+```
 
 ### Service configuration with `docker-compose`
 

docs/install/containers/examples/nginx-volto-plone.md

@@ -10,6 +10,7 @@ html_meta:
 
 Very simple setup with only one backend and data being persisted in a Docker volume.
 
+Nginx in this example is used as a [reverse proxy](https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/").
 
 ## Setup
 
@@ -75,6 +76,10 @@ server {
 }
 ```
 
+```{note}
+`http://plone.localhost/` is the url you will be using to access the website.
+You can either use `localhost`, or add it in your `etc/hosts` file or DNS to point to the docker host IP.
+```
 
 ### Service configuration with `docker-compose`