Bug description
The step install is: 1、download the 6.0.0rc package. apache_superset-6.0.0rc1-source.tar.gz
2、using python3.11, install the package pip install apache_superset-6.0.0rc1-source.tar.gz
3、init superset db upgrade superset fab create-admin superset init
4、run superset run -h 0.0.0.0 -p 8088 --with-threads --reload
follow the step, everything is ok, but when i open the web page. there is error.
which not exist static content in directory.
what is wrong with it? can anyone can help me. thanks very much to let me know, thks.
Comment From: dosubot[bot]
Hi @bxter! I'm Dosu and I’m helping the superset team.
The missing static content error happens because the Superset source tarball does not include pre-built frontend assets. After installing from source, you need to manually build these assets using Node.js and npm in the superset-frontend
directory.
To fix this, run the following commands from your Superset source directory:
cd superset-frontend
npm ci
npm run build
This will generate the required static files (like 500.html
) in superset/static/assets
. After building, restart Superset and the web UI should load correctly.
This manual frontend build step is required for source installs and is documented in the Dockerfile.from_local_tarball and Makefile. The webpack config confirms these assets are generated only after running the build process (webpack.config.js).
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
Comment From: bxter
I use the down package from https://dist.apache.org/repos/dist/dev/superset/6.0.0rc1/
https://dist.apache.org/repos/dist/dev/superset/6.0.0rc1/apache_superset-6.0.0rc1-source.tar.gz
how to install with it. can anyone give a completed install step. thks very much.
Comment From: dosubot[bot]
Here’s a complete step-by-step guide to install Superset 6.0.0rc1 from the source tarball:
Requirements:
- Python 3.10 or 3.11 (Python 3.12 is not supported)
- Node.js 20.x (recommended: 20.18.3)
- npm 10.8.1 or newer
- OS-level build dependencies (e.g. build-essential
, libssl-dev
, libffi-dev
, python3-dev
, etc.) details
Install Steps:
-
Install OS dependencies
For Ubuntu/Debian:bash sudo apt-get update sudo apt-get install build-essential libssl-dev libffi-dev python3-dev libsasl2-dev libldap2-dev default-libmysqlclient-dev
For other OS, see docs. -
Install Node.js and npm
Use Node.js 20.x and npm 10+ (see.nvmrc
andpackage.json
requirements):bash curl -sL https://deb.nodesource.com/setup_20.x | sudo -E bash - sudo apt-get install -y nodejs
-
Create and activate a Python virtual environment
bash python3.11 -m venv venv source venv/bin/activate
-
Extract the source tarball
bash tar -xvf apache_superset-6.0.0rc1-source.tar.gz cd apache_superset-6.0.0rc1-source
-
Install Python dependencies and Superset
bash pip install --upgrade pip setuptools pip install -r requirements/base.txt pip install .
-
Build frontend assets
This step is critical and must be done before running Superset:bash cd superset-frontend npm ci npm run build cd ..
This will generate the required static files (like500.html
) insuperset/static/assets
(reference, webpack config). -
Initialize Superset and create admin user
bash export FLASK_APP=superset export SUPERSET_SECRET_KEY='your-secret-key' superset db upgrade superset fab create-admin superset init
-
(Optional) Load example data
bash superset load-examples
-
Run Superset server
bash superset run -h 0.0.0.0 -p 8088 --with-threads --reload
Common pitfalls:
- Skipping the frontend build step (npm ci
+ npm run build
) will result in missing static assets and web UI errors.
- Using unsupported Python or Node.js versions can cause install/build failures.
Let me know if you hit any specific errors during these steps!
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
Comment From: sadpandajoe
@bxter just wondering why not https://pypi.org/project/apache-superset/6.0.0rc1/ for install?