Easier installation with docker when exposing seelf using the internal Traefik proxy
YuukanOO opened this issue ยท 2 comments
For now the installation is a bit clunky because I wanted to show how we can leverage the traefik proxy deployed by seelf at startup to also expose seelf under the same domain.
Maybe that was a mistake and I should show the easier way using docker run -d -e "SEELF_ADMIN_EMAIL=admin@example.com" -e "SEELF_ADMIN_PASSWORD=admin" -v "/var/run/docker.sock:/var/run/docker.sock" -v "seelfdata:/seelf/data" --restart=unless-stopped -p "8080:8080" yuukanoo/seelf
which bind directly the server on the host.
But since I really want to ease the exposing of seelf using a specific subdomain and the certificate generation, I've been tinkering with configuring the traefik with a dynamic file exposing seelf (without requiring specific label).
With this in mind, we can conditionnaly output this file if some configuration option is here, such as SEELF_SUBDOMAIN
and the command will then be docker run -d -e "SEELF_SUBDOMAIN=seelf"-e "SEELF_ADMIN_EMAIL=admin@example.com" -e "SEELF_ADMIN_PASSWORD=admin" -v "/var/run/docker.sock:/var/run/docker.sock" -v "seelfdata:/seelf/data" --restart=unless-stopped yuukanoo/seelf
.
Also, add notes about how to update seelf to the latest version. Since the configuration is written at startup, the docker process should be an easy one.
I've reconsidered this as it seems clunky as hell. So the final solution was to provide a specific section in the documentation about how to expose seelf using the inner proxy.
๐ This issue has been resolved in version 1.0.1 ๐
The release is available on:
v1.0.1
- GitHub release
Your semantic-release bot ๐ฆ๐