From 9515778b2571f9e5b77d9e081f8b8e227275769a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Peters?= Date: Mon, 29 Jan 2018 08:15:23 +0100 Subject: [PATCH] Update third_party-portainer.md --- docs/third_party-portainer.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/third_party-portainer.md b/docs/third_party-portainer.md index c15f867e0..ea6c01d35 100644 --- a/docs/third_party-portainer.md +++ b/docs/third_party-portainer.md @@ -1,6 +1,6 @@ In order to enable Portainer, the docker-compose.yml and site.conf for Nginx must be modified. -1\. docker-compose.yml: Insert this block for portainer +1\. Create a new file `docker-compose.override.yml` in the mailcow-dockerized root folder and insert the following configuration ``` portainer-mailcow: image: portainer/portainer @@ -16,7 +16,7 @@ In order to enable Portainer, the docker-compose.yml and site.conf for Nginx mus aliases: - portainer ``` -2a\. data/conf/nginx/site.conf: Just beneath the opening line, at the same level as a server { block, add this: +2a\. Create `data/conf/nginx/portainer.conf`: ``` upstream portainer { server portainer-mailcow:9000; @@ -28,7 +28,7 @@ map $http_upgrade $connection_upgrade { } ``` -2b\. data/conf/nginx/site.conf: Then, inside **both** (ssl and plain) server blocks, add this: +2b\. Insert a new location to the default mailcow site by creating the file `data/conf/nginx/site.portainer.custom`: ``` location /portainer/ { proxy_http_version 1.1; @@ -51,8 +51,9 @@ map $http_upgrade $connection_upgrade { } ``` -3\. Then you need to pull the container and restart Nginx: +3\. Apply your changes: ``` docker-compose up -d && docker-compose restart nginx-mailcow ``` + Now you can simply navigate to https://${MAILCOW_HOSTNAME}/portainer/ to view your Portainer container monitoring page. You’ll then be prompted to specify a new password for the **admin** account. After specifying your password, you’ll then be able to connect to the Portainer UI.