I discovered that applying sikka settings differs in production than in development.
In development, --settings can be used and that's fine.
In production, --settings cannot be used so what we normally do is export METEOR_SETTINGS through cat path-to-settings-file so the settings get set in the environment variable.
It turns out, although all other settings are applied while sikka ignores them in production and only looks for SIKKA* environment variables.
This is either a bug or intentional, either way, it should be documented.
I discovered that applying sikka settings differs in production than in development.
In development, --settings can be used and that's fine.
In production, --settings cannot be used so what we normally do is export METEOR_SETTINGS through cat path-to-settings-file so the settings get set in the environment variable.
It turns out, although all other settings are applied while sikka ignores them in production and only looks for SIKKA* environment variables.
This is either a bug or intentional, either way, it should be documented.