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

Daemonized HTTP server? several deployment options including Gunicorn #32

Open
lee212 opened this issue Apr 26, 2013 · 0 comments
Open

Comments

@lee212
Copy link
Contributor

lee212 commented Apr 26, 2013

At some point, the flask needs to come with stand alone HTTP server in production. Fortunately, there are several options that we can choose to run flask_cm application.

Gunicorn looks quite simple so it would be better to leave a short note here.

  • Install gunicorn: pip install gunicorn
  • Run gunicorn: gunicorn flask_cm/server:app
  • With other options: gunicorn -w 4 -b 127.0.0.1:5000 flask_cm/server:app
  • (-w number of workers, -b binding name with port number)

Also, we can add a proxy server to protect services from any type of compromising situations. Gunicorn can comes with Nginx.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant