Docker swarm setup W/ secrets and external postgres

(#1298) Feature Under consideration self-hosting

2mo agoby RexSystem edited originally by @kaibsora on GitHub

Problem

If you already have a docker swarm setup with traefik as your reverse proxy you dont need to add another vm/docker host. also enables high availability. If you also have an external postgres db/cluster, you shouldn't need to make a new one.

Proposal

There should be additional documentation that points out the changes in the compose file for swarm setup, as well as changes noting swarm secret creation/usage in the stack, rather than insecure .env files. There should also be information on how to setup/configure a running postgres cluster for integration with fluxer.

History

1 comment

RexSystem 1 vote 2mo ago originally by @dantuki on GitHub

Hello :D I agree that supporting existing infrastructure is important for adoption, especially in production environments. Many developers and organizations already have a reverse proxy such as Traefik and an existing database cluster running. Requiring additional services can make evaluation and deployment more complex than necessary. Having dedicated documentation for Docker Swarm deployments, secret management through Swarm Secrets, and integration with external PostgreSQL instances would likely make Fluxer easier to adopt in enterprise environments. Even if these configurations are not the primary deployment path, providing examples and best practices could help users integrate Fluxer into existing infrastructure without duplicating services.

Permalink