You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am curious about your opinions, what do you think, would make it sense to add also a web-proxy to the træfik example ?
Background:
We have now a nice example about 'easy' load balancing, what we are still missing is a 'easy' example for domain handling.
Example
We show in an example how you can a setup including:
two instances
traefik as load-blancer
caddy-proxy a webserver (caddy) proxy in front of traefik
(I use already caddy-proxy in production, I still need to publish the container :) )
--> people browse to plone.example(caddy-proxy) which speaks to traefik -> which does the load-balancing.
This is maybe already too much for the 'normal' docs, but it is time to start the preparation for the trainings for PloneConf 2017 and I have the idea to use a setup like this for the 'deployment training'
:)
The text was updated successfully, but these errors were encountered:
I think what the setup is primarily missing now is a caching proxy. I have a Docker Swarm configuration somewhere with hitch -> varnish -> traefik -> plone setup but it is not a very simple one.
If there are static files to be served then adding Caddy makes sense. Otherwise I would just try to configure Traefik to do SSL etc. directly.
My idea was/is to use caddy in front just to proxy my domain name to a port something like:
Start the proxy
docker run -d -p $PORT:$PORT -v /var/run/docker.sock:/tmp/docker.sock:ro caddy-proxy
Start Plone
docker run -e VIRTUAL_HOST=plone.io -p $PORT:PORT plone
Given the simple setup that your one docker host is reachable by plone.io you can use
the environment setting -e VIRTUAL_HOST=plone.io.
Now you can go to plone.io:$PORT/ and you have your plone site.
This would be of course different for swarm, kubernetes or the setup of your choise.
This could be also changed to point to varnish and/or traefik.
I am collecting ideas and setups for the moment, so hell yeah if you want to share your hitch -> varnish -> plone -> treafik -> plone that would be awesome !
The idea is to have some 'easy' and 'advanced' setups/examples.
All this is meant for the training during the upcoming PloneConf.
The training docs will be on training.plone.org later on, so yeah we do not have to worry that it may be to advanced, at least not for now :)
@ju55i @avoinea
I am curious about your opinions, what do you think, would make it sense to add also a web-proxy to the træfik example ?
Background:
We have now a nice example about 'easy' load balancing, what we are still missing is a 'easy' example for domain handling.
Example
We show in an example how you can a setup including:
(I use already caddy-proxy in production, I still need to publish the container :) )
--> people browse to plone.example(caddy-proxy) which speaks to traefik -> which does the load-balancing.
This is maybe already too much for the 'normal' docs, but it is time to start the preparation for the trainings for PloneConf 2017 and I have the idea to use a setup like this for the 'deployment training'
:)
The text was updated successfully, but these errors were encountered: