Update SELF-HOSTING.md
This commit is contained in:
parent
c428cc7658
commit
7be48e3f4a
@ -62,7 +62,8 @@ mysql> quit;
|
|||||||
|
|
||||||
If your set up was correct, you should now be able to run:
|
If your set up was correct, you should now be able to run:
|
||||||
|
|
||||||
`flask db upgrade`
|
`flask db init`
|
||||||
|
`flask db migrate`
|
||||||
|
|
||||||
#### Step 3: Setting up Gunicorn and Supervisor
|
#### Step 3: Setting up Gunicorn and Supervisor
|
||||||
When you run the server with flask run, you are using a web server that comes with Flask. This server is very useful during development, but it isn't a good choice to use for a production server because it wasn't built with performance and robustness in mind. Instead of the Flask development server, for this deployment I decided to use gunicorn, which is also a pure Python web server, but unlike Flask's, it is a robust production server that is used by a lot of people, while at the same time it is very easy to use. [ref](https://blog.miguelgrinberg.com/post/the-flask-mega-tutorial-part-xvii-deployment-on-linux)
|
When you run the server with flask run, you are using a web server that comes with Flask. This server is very useful during development, but it isn't a good choice to use for a production server because it wasn't built with performance and robustness in mind. Instead of the Flask development server, for this deployment I decided to use gunicorn, which is also a pure Python web server, but unlike Flask's, it is a robust production server that is used by a lot of people, while at the same time it is very easy to use. [ref](https://blog.miguelgrinberg.com/post/the-flask-mega-tutorial-part-xvii-deployment-on-linux)
|
||||||
|
Reference in New Issue
Block a user