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

[fading sparrow]

I’ve put together an all-in-one script for self-hosting Ente where all configuration is centralized in a single compose.yaml. The setup includes Caddy for multi-domain handling, reverse proxying, and automatic TLS, and the setup wizard performs a dig check to verify DNS resolution.

1. Run setup wizard
2. It generates a .env file
3. Bring everything up with a single docker compose command (including reverse proxy and HTTPS)

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 file and configure it entirely via environment variables? The goal is for .env to be the single source of truth.

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

[glass marsh]

Sorry, I could not find an answer.
-# If your issue is resolved, use </solved:1410327008973557843> to mark this thread as solved. Use </docsearch:1378409618417647708> if you want to ask something else.

🔍 Similar Solved Posts

Found some similar posts that might help:

📋 Check these out:

Upload failed - Domaine name - IPV6 (56%)
Setting with Compose install (55%)

Searched 74 solved posts