Superset not running. Error in config file

[masterlittle]

Make sure these boxes are checked before submitting your issue - thank you!

• I have checked the superset logs for python stacktraces and included it here as text if any
• I have reproduced the issue with at least the latest released version of superset
• I have checked the issue tracker for the same issue and I haven't found one similar
  When giving the SUPERSET_CONFIG_PATH as /home/superset/superset_config.py, I am getting the following error --
  Traceback (most recent call last):
  File "/usr/local/bin/superset", line 12, in
  from superset.cli import manager
  File "/usr/local/lib/python2.7/dist-packages/superset/init.py", line 21, in
  from superset import utils, config # noqa
  File "/usr/local/lib/python2.7/dist-packages/superset/config.py", line 350, in
  override_conf = imp.load_source('superset_config', os.environ[CONFIG_PATH_ENV_VAR])
  File "/home/superset/superset_config.py", line 41, in
  with open(PACKAGE_FILE) as package_file:
  IOError: [Errno 2] No such file or directory: u'/home/superset/static/assets/package.json'

Looks like it is searching for the assets in a relative path to the config file. How to resolve this?

Superset version

0.20.6

Expected results

Actual results

Steps to reproduce

[amoussoubaruch]

@masterlittle Please Are you following step by step superset installation?

[masterlittle]

Yeah. It works if I don't give a config path. And now I got it working after hardcoding the BASE_DIR variable in my config file.
I had to change the value of BASE_DIR to '/usr/local/lib/python2.7/dist-packages/superset/'

I think the issue was that this line--
BASE_DIR = os.path.abspath(os.path.dirname(file))

It keeps the BASE_DIR as the same directory as the config file and does not build the static/assets path there.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

[nileio]

faced the same exact issue and fixed it by changing the BASE_DIR as @masterlittle suggested. Thanks
it is apparently a bug