stevecorya/agassi repository overview

⁠Agassi

Agassi is inspired by the setup detailed at Docker Swarm Rocks⁠. When Traefik dropped support for distributed certificate storage, it created a situation all certificates were stored locally on a single machine. This removed redundency from the setup.

Taking advantage of etcd and Docker Swarm's built-in state management, Agassi is able to run without the use of generative templates. Each agassi service is mapped to a virtual host, which are created by the client and retrieved by the server.

By using Agassi, you are accepting the Let's Encrypt Subscriber Agreement⁠.

⁠Configuration

* this must end with a dot, e.g., subdomain.example.com.

⁠Labels

• page.agassi.domain set to your target domain e.g. example.com
• page.agassi.auth see Authorization⁠ for how to generate an auth string
• page.agassi.options.target the service access address for example http://myservice:80 All options prefixed with page.agassi.options. are camel-cased (set prependPath with the label page.agassi.opts.prepend-path) and passed to node-http-proxy⁠. Pass the labels into your swarm compose file.

services:
  service-01:
    image:
    deploy:
      labels:
        page.agassi.domain: example.com
        page.agassi.options.target: http://service-01:80

⁠Flow

Agassi requires the use of two seperate services, a client (ACME, etcd, and docker) and a server (HTTPS).

⁠Client

Client spins up.

Client checks for existing services and makes sure certificates are current.

Client subscribes to new service updates.

⁠Server

Server spins up.

Starts listening to HTTPS requests.

⁠Authorization

To generate a basic auth parameter:

echo $(htpasswd -n -B -C 4 user | base64 -w 0)

To generate a default and ACME account key

openssl genrsa 4096 | docker secret create my_key -