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.

Sign up for GitHub

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

Jump to bottom

docs(contributing): added note for creating SECRET_KEY #23417

Merged
merged 2 commits into from
Mar 22, 2023
Merged

docs(contributing): added note for creating SECRET_KEY #23417

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9a01d7c
Added a note for creating SECRET_KEY
Govindarajan-D Mar 18, 2023
2e8d1d4
Changed the command for appending instead of overwriting
Govindarajan-D Mar 18, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/docs/contributing/local-backend.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,8 @@ pip install -r requirements/testing.txt
pip install -e .

# Initialize the database
# Note: For generating a SECRET_KEY if you haven't done already, you can use the command:
# echo "SECRET_KEY='$(openssl rand -base64 42)'" | tee -a superset_config.py
Copy link
Member

@nytai nytai Mar 20, 2023 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If running with FLASK_ENV = development this shouldn't be necessary for running, but still good to have this so users aren't confused when trying to run prod

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If running with FLASK_ENV = development this shouldn't be necessary for running, but still good to have this so users aren't confused when trying to run prod

@nytai Yeah. that was the idea in the change that @dpgaspar made in #23186, but it's not working, as per my issue #23288

Maybe you have an idea how to make #23186 work as intended.

superset db upgrade

# Create an admin user in your metadata database (use `admin` as username to be able to load the examples)
Expand Down