-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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
How to daemonize superset process #2123
Comments
I found that I can close the controlling terminal and the gunicorn still run as a daemon. |
What about letting your init system take care of superset? |
I've written a simple systemd service:
|
@petroswork nice |
Thanks for this. I had to make the following change on Azure:
|
@josebrwn Mine was meant as a user service, i.e. appears in |
With few improvements works well for me. #superset.service [Service] [Install] |
For the record we use chef/runit at Airbnb. Hopefully we get to ship with some Linux distros that will take care of that eventualy :) |
Hi running the script from @fuzaro I'm getting |
@pastarace change
|
Would recommend using a straight |
@liptanbiswas can I use my own configuration file as well? Does this work?? please assist [Service] [Install] |
@nagaraju02 Yes you can. You see in the script I pasted above, I am putting
However, since you have installed the application in |
@liptanbiswas thanks a lot! Thanks It worked! |
Use the comando nohup before the command and put & in the final example: nohup superset runserver -p 8088 & |
where to add this file and what is the case of the virtual environment?? |
Can any one help me out what what in case supercet Is running on python virtual environment? how we can get into python virtual environment and how we can setup this process |
@GOPIPACHA The python environment can be specified in the .service file as "Environment=PYTHONPATH=/home/rspl_test/venv_s/bin:$PYTHONPATH" similar to what is done in above examples. The service file will automatically activate this environment |
the .service file must be in /etc/systemd/system |
Make sure these boxes are checked before submitting your issue - thank you!
Superset version
0.15.0
Expected results
Detaches the server from the controlling terminal and enters the background
Actual results
can't realize running superset at backend
Steps to reproduce
gunicorn is superset's server, I add the parameter
-D --daemon
in bin.superset.run_server(), but don't work.Is there any other way s to detaches the server from the controlling terminal and enters the background?
The text was updated successfully, but these errors were encountered: