Deploy - Flask
Last updated
Was this helpful?
Last updated
Was this helpful?
In this lesson we'll cover:
Pipfiles
Procfiles
Configuration
Before we get started, we need a couple tools. Let's install a few things and set them up.
Install pipenv via your terminal.
Protip: Pipenv is a package that will help us manage Pipfiles. We can also install packages with pipenv, which will be similar to how regular
pipinstall works, but it also automatically adds the package to the Pipfile.
Your Pipfile is a list of dependencies for your Flask app. It replaces the old way of keeping track of this, where you would use a freeze command to create a requirements.txt file. Now instead we will have Pipfile and Pipfile.lock. We'll cover the lock file in a moment. For now, let's set up your Pipfile.
Tip: You may see a lot of code on the internet that still uses requirements.txt. Remember, Pipfiles are a reaplcement for this. We do not need a requirements.txt!
According to the , when you run the pipenv --python 3 command, if you don't have a Pipfile already, one will be generated for youthat looks like this:
This is a pretty good start. The only section we really need to put any thinking into is the [packages] section. Here, we just need to include any packages we actually import and use. This means, don't worry about sub-dependencies as they will be installed automatically!
Gunicorn is a server that supports concurrent processes. It will make your Heroku app feel faster and be better utilized.
The pipenv command above both installs gunicorn and adds it to the Pipfile. If you installed with the pip or pip3 commands, you will need to manually type the name gunicorn into your Pipfile. We're also going to want to type in flask as a package we are using. Your Pipfile should not look something like this:
Now that we have Gunicorn installed, let's use it! Create a file called Procfile in the top level folder of you app.
Remember the capital
PinProcfile!
Your Procfile should look like the following:
The "server" in the above command refers to the name of your entry point. So, it assumes you called your main file server.py. If you called your main file app.py then it would look like web: gunicorn app:app
Tip: You can add a release step as well, which runs after the build succeeds. For example, this is often used for database migrations.
Now we're ready to deploy! Create a Heroku app, then add, commit, and push to Heroku.
You can add configuration variables from the command line or via the GUI if you log into Heroku's website.
Solving Performance Issues: If after your app is up and running, you are experiencing performance issues, take a read through and configure WEB_CONCURRENCY and/or preload settings accordingly.