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.

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

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

Merged
merged 2 commits into from
Mar 22, 2023

Conversation

Govindarajan-D
Copy link
Contributor

@Govindarajan-D Govindarajan-D commented Mar 18, 2023

SUMMARY

In the steps of installing locally the flask backend, if the SECRET_KEY has not been already generated, I thought adding a step for generating the SECRET_KEY would be good, as I was searching for it.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

BEFORE

image

AFTER

Highlighted the newly added comment
image

TESTING INSTRUCTIONS

There are no steps necessary for testing as this is a documentation change.

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

@Govindarajan-D Govindarajan-D marked this pull request as ready for review March 18, 2023 14:54
Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Congrats on making your first PR and thank you for contributing to Superset! 🎉 ❤️

We hope to see you in our Slack community too! Not signed up? Use our Slack App to self-register.

@@ -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

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.

@rusackas rusackas merged commit fae3ad0 into apache:master Mar 22, 2023
@mistercrunch mistercrunch added 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 3.0.0 labels Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels size/XS 🚢 3.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants