Automatic SSL and load balancing


Because Swarmlet activates Docker Swarm mode, you can run your applications in 'highly available' Docker containers across your swarm. The application containers will be distributed on the swarm, this can be configured in your project docker-compose.yml file under the deploy key.

Traefik and GlusterFS

traefik diagram

Swarmlet uses Traefik for load balancing. Traefik detects new applications and listens for any configuration updates. Traefik will attempt to generate a SSL certificate for each frontend service in your application stack using Let's Encrypt.

Certificates are stored on a GlusterFS volume, mounted at /mnt/gfs. In the case where a swarm node goes offline, the certificates are still available on other nodes in the GlusterFS pool.

Let's encrypt rate limiting

Use the Let's Encrypt staging environment to prevent exceeding the rate limit while developing.
To change to the staging/production server, update the Traefik configuration.


Example project configuration

Add a .env file to the root of your project, containing:


To enable load balancing on a service and expose it to the web, add the highlighted labels and networks to your frontend service(s):

version: "3.7"
image: ${SWARMLET_REGISTRY}/test-app
build: .
mode: replicated
replicas: 3
- traefik.enable=true
# Specify the internal container port to expose
# Specify the domain
- traefik.http.routers.test-app.rule=Host(`test-app.${DOMAIN}`)
# Redirect HTTP traffic to HTTPS
- traefik.http.routers.test-app.entrypoints=http,https
- traefik.http.routers.test-app.middlewares=redirect@file
- traefik-public
external: true

Traefik configuration

Pull the router repo from the swarm:

git clone git@my-swarm:router
cd router

Uncomment the following line in the docker-compose.yml file.

# - --certificatesresolvers.letsencrypt.acme.caserver=""

Save and commit your changes.
Push to re-deploy Traefik with it's new settings:

git push origin master