Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Comments

@serkandurusoy
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant