mirror of
https://github.com/apache/superset.git
synced 2026-04-07 18:35:15 +00:00
392d8a8107
* starter make file * yea * move messaging to config * Delete Makefile * remove * checkout * check for db generic errors * checkout bad files * add proper message * add docs for new permissions codes * Update superset/errors.py Co-authored-by: AAfghahi <48933336+AAfghahi@users.noreply.github.com> * Update superset/errors.py Co-authored-by: AAfghahi <48933336+AAfghahi@users.noreply.github.com> * rename var * starter regex * fix * fix * fix linting * update test * yerp * fixed test * added regex * Apply suggestions from code review Co-authored-by: Beto Dealmeida <roberto@dealmeida.net> * address comments * update docs * prettier * fux * add space * Update errors.py * Update types.ts Co-authored-by: AAfghahi <48933336+AAfghahi@users.noreply.github.com> Co-authored-by: Beto Dealmeida <roberto@dealmeida.net>
Here's the source to the documentation hosted at superset.apache.org
The site runs on the Gatsby framework and uses docz for it's
Documentation subsection.
Getting Started
cd docs/
npm install
npm run start
# navigate to localhost:8000`
To Publish
To publish, the static site that Gatsby generates needs to be pushed
to the asf-site branch on the
apache/superset-site
repository. No need to PR here, simply git push.
# Get in the docs/ folder in the main repo
cd ~/repos/superset/docs
# have Gatsby build the static website, this puts in under `docs/public`
npm run build
# go to the docs repo
cd ~/repos/superset-site
# checkout the proper branch
git checkout asf-site
# BE CAREFUL WITH THIS COMMAND
# wipe the content of the repo
rm -rf *
# copy the static site here
cp -r ~/repos/superset/docs/public/ ./
# git push
git add .
git commit -m "relevant commit msg"
git push origin asf-site
# SUCCESS - it should take minutes to take effect on superset.apache.org