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

How to run Superset with gunicorn in virtualenv? #7890

Closed
2 of 3 tasks
syazshafei opened this issue Jul 18, 2019 · 2 comments
Closed
2 of 3 tasks

How to run Superset with gunicorn in virtualenv? #7890

syazshafei opened this issue Jul 18, 2019 · 2 comments

Comments

@syazshafei
Copy link

syazshafei commented Jul 18, 2019 •
edited

A clear and concise description of what the bug is.

Expected results

Can run Superset in production mode in virtualenv

Actual results

what actually happens.

Environment

(please complete the following information):

  • superset version: 0.28.1
  • python version: 3.6
  • node.js version: 10.16.0
  • npm version: 6.9.0

Checklist

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 there are 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.
@issue-label-bot
Copy link

Issue Label Bot is not confident enough to auto-label this issue. See dashboard for more details.

@mistercrunch
Copy link
Member

Please refer to the gunicorn docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mistercrunch @syazshafei