create a domain helper image

[pigeonflight]

the domain helper image takes an enviroment variable

VIRTUAL_HOST=example.com

It uses this to create a virtual_hosting mapping within Zope.

[pigeonflight]

The domain helper works in conjuction with https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion/
When you launch conferencd ...
make sure that you set the following environment variables:
VIRTUAL_HOST, LETSENCRYPT_HOST and SITE_PATH.

VIRTUAL_HOST is the domain name for the site
LETSENCRYPT_HOST must set to ensure that a secure certificate is issued for https serving of the site.
The SITE_PATH is the path to your plone site relative to the root of the application server (the site path is most commonly set to Plone)

[pigeonflight]

docker run --detach \
    --name nginx-proxy \
    --publish 80:80 \
    --publish 443:443 \
    --volume /etc/nginx/certs \
    --volume /etc/nginx/vhost.d \
    --volume /usr/share/nginx/html \
    --volume /var/run/docker.sock:/tmp/docker.sock:ro \
    jwilder/nginx-proxy

then

docker run --detach \
    --name nginx-proxy-letsencrypt \
    --volumes-from nginx-proxy \
    --volume /var/run/docker.sock:/var/run/docker.sock:ro \
    --env "DEFAULT_EMAIL=mail@yourdomain.tld" \
    jrcs/letsencrypt-nginx-proxy-companion

then

docker run --detach
--name vhost_helper \
--volumes-from nginx-proxy \
--volume /var/run/docker.sock:/var/run/docker.sock:ro \
alteroo/vhost_helper

finally ... launch your site

 docker run --detach \
    --name your-site \
    --env "VIRTUAL_HOST=subdomain.yourdomain.tld" \
    --env "LETSENCRYPT_HOST=subdomain.yourdomain.tld" \
    --env "SITE_PATH=Plone" \
    alteroo/conferencd

[pigeonflight]

As an alternative approach, automate the passing of something like this to nginx-proxy:

rewrite ^/(.*)$ /VirtualHostBase/https/$host:80/$SITE_PATH/VirtualHostRoot/$1 break;