-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
overriding config with SUPERSET_CONFIG_PATH env variable not working #2982
Comments
I have the same issue. It looks like superset doesn't initialize the config correctly from ENV var. If you run
You'll get the sqlite path. I found however that if I don't configure
This code path may be a bit wonky. |
How are you starting superset? I mean, how do you tell superset which config to read. |
Easy workaround is to just use the |
@xrmx I set the environment variable: SUPERSET_CONFIG_PATH: /home/superset/.superset/superset_config.py |
How do I add my configuration file to PYTHONPATH? |
It's been a while since I've done this but if I recall correctly it's like this: https://superset.incubator.apache.org/faq.html#why-does-flask-fab-or-superset-freezed-hung-not-responding-when-started-my-home-directory-is-nfs-mounted |
Thanks. |
Make sure these boxes are checked before submitting your issue - thank you!
Superset version
0.18.4
Expected results
creating tables in postgres
Actual results
created sqllite db
Steps to reproduce
SQLALCHEMY_DATABASE_URI = 'postgresql://supersetdb:xxx@somehost/supersetdb'
The database is outside of the docker container, user and password are correct, it loads the config.py, at least it says so.
The text was updated successfully, but these errors were encountered: