4 replies

Self-hosting Ente with one compose file. Q: Can Museum be fully env-based?

DocumentationConfig

PhotosMiscellaneous

I’ve put together an all-in-one script for self-hosting Ente where all configuration is centralized in a single

compose.yaml

compose.yaml

compose.yaml

compose.yaml. The setup includes Caddy for multi-domain handling, reverse proxying, and automatic TLS, and the setup wizard performs a

dig

dig

dig

dig check to verify DNS resolution.

1. Run setup wizard
2. It generates a

.env

.env

file
3. Bring everything up with a single

docker compose

docker compose

docker compose

docker compose command (including reverse proxy and HTTPS)

bash <(curl -sSL https://raw.githubusercontent.com/polarhive/dots/main/hosts/pina/setup.sh)

bash <(curl -sSL https://raw.githubusercontent.com/polarhive/dots/main/hosts/pina/setup.sh)

bash <(curl -sSL https://raw.githubusercontent.com/polarhive/dots/main/hosts/pina/setup.sh)

bash <(curl -sSL https://raw.githubusercontent.com/polarhive/dots/main/hosts/pina/setup.sh)

Question: Is there a supported way to run Museum without a

museum.yaml

museum.yaml

museum.yaml

museum.yaml file and configure it entirely via environment variables? The goal is for

.env

.env

to be the single source of truth.

I currently auto-generate

museum.yaml

museum.yaml

museum.yaml

museum.yaml, but I’m wondering whether full environment-variable–based configuration is supported or planned upstream.

GitHub

systems managed using nix . Contribute to polarhive/dots development by creating an account on GitHub.