You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Config is currently set with environment variables. Env vars are set in the docker compose file. The docker compose file is basically locked since we don't want to force node operators to update it.
Solution: Check for a /usr/src/app/shared/config.json file, which is mapped to $SATURN_HOME/shared/config.json on the host filesystem.
Do we still need this? Or is the .env load on docker compose good enough for now? I think it would be good to scope deployment-specific configs from application-specific ones.
Config is currently set with environment variables. Env vars are set in the docker compose file. The docker compose file is basically locked since we don't want to force node operators to update it.
Solution: Check for a
/usr/src/app/shared/config.json
file, which is mapped to$SATURN_HOME/shared/config.json
on the host filesystem.L1-node/docker-compose.yml
Line 25 in 9e30610
This will allow us to configure behavior without changing the docker compose file. Config files are also more flexible than env vars.
Let's implement this when the current config system becomes a pain point. There are more pressing issues atm (Rhea/Lassie).
The text was updated successfully, but these errors were encountered: