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
Applying settings in production/development should be documented more clearly. Currently, there is a problem and METEOR_SETTINGS is ignored by Sikka!
#19
Open
serkandurusoy opened this issue
Apr 18, 2015
· 0 comments
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: