-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Easier installation with docker when exposing seelf using the internal Traefik proxy #12
Labels
Comments
YuukanOO
added a commit
that referenced
this issue
May 24, 2023
Remove reference to traefik labels to ease the onboarding and add a specific section related to exposing seelf using the traefik proxy managed by seelf.
Merged
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. |
YuukanOO
added a commit
that referenced
this issue
May 25, 2023
* fix: wrong created location header for session * fix: add HTTP_SECURE configuration variable * chore: move the logic for the first user account creation in app/command * chore: closes #12 makes the getting started much easier
YuukanOO
added a commit
that referenced
this issue
May 25, 2023
* fix: wrong created location header for session * fix: add HTTP_SECURE configuration variable * chore: move the logic for the first user account creation in app/command * chore: closes #12 makes the getting started much easier
🎉 This issue has been resolved in version 1.0.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 bedocker 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.
The text was updated successfully, but these errors were encountered: