[Self-Hosting] Fatal crash on startup when ENVIRONMENT=production (Missing Billing Config)
Hi team,
I am self-hosting the Museum server using Docker Compose (via Coolify). I recently switched my setup to
While my main config and credentials files are loading correctly, the server immediately crashes with a fatal error regarding missing "Black Friday" configuration files.
The Error:
Context:
* Deployment: Docker Compose (Coolify)
* Env:
* Issue: The server refuses to boot unless I manually volume-mount a dummy
My Question:
Is it intended behavior that a self-hosted production instance requires these internal commercial/billing configuration files to exist? It seems odd that the server panics on a missing Black Friday offer config when I am just trying to run a standard self-hosted instance.
Ideally, shouldn't these default to "disabled" or handle the missing file gracefully if the billing system isn't being used?
Thanks for your help!
I am self-hosting the Museum server using Docker Compose (via Coolify). I recently switched my setup to
ENVIRONMENT=production so that I can properly utilize configurations/production.yaml and credentials.yaml.While my main config and credentials files are loading correctly, the server immediately crashes with a fatal error regarding missing "Black Friday" configuration files.
The Error:
Context:
* Deployment: Docker Compose (Coolify)
* Env:
ENVIRONMENT=production* Issue: The server refuses to boot unless I manually volume-mount a dummy
data/billing/black-friday.json file.My Question:
Is it intended behavior that a self-hosted production instance requires these internal commercial/billing configuration files to exist? It seems odd that the server panics on a missing Black Friday offer config when I am just trying to run a standard self-hosted instance.
Ideally, shouldn't these default to "disabled" or handle the missing file gracefully if the billing system isn't being used?
Thanks for your help!
