application.py

import os

from flask import Flask
from whitenoise import WhiteNoise

from app import create_app

PROJECT_ROOT = os.path.dirname(os.path.abspath(__file__))
STATIC_ROOT = os.path.join(PROJECT_ROOT, 'app', 'static')
STATIC_URL = 'static/'

flask_app = Flask('app')

create_app(flask_app)

application = WhiteNoise(flask_app.wsgi_app, STATIC_ROOT, STATIC_URL, max_age=WhiteNoise.FOREVER)
remove wsgi.py - always serve with whitenoise We're now running our app as a wsgi app locally, so don't need to distinguish between the two processes by having wsgi and application.py whitenoise just serves static files nicely - we don't lose anything by doing that locally. 2017-11-07 11:50:13 +00:00			`import os`

remove flask-script flask-script has been deprecated by the internal flask.cli module, but making this carries a few changes with it * you should add FLASK_APP=application.py and FLASK_DEBUG=1 to your environment.sh. * instead of using `python app.py runserver`, now you must run `flask run -p 6012`. The -p command is important - the port must be set before the config is loaded, so that it can live reload nicely. (https://github.com/pallets/flask/issues/2113#issuecomment-268014481) * find available commands by just running `flask`. * run them using flask. eg `flask list_routes` * define new tasks by giving them the decorator `@app.cli.command('task-name')`. Task name isn't needed if it's just the same as the function name. Alternatively, if app isn't available in the current scope, you can invoke the decorator directly, as seen in app/commands.py 2017-11-06 13:07:21 +00:00			`from flask import Flask`
remove wsgi.py - always serve with whitenoise We're now running our app as a wsgi app locally, so don't need to distinguish between the two processes by having wsgi and application.py whitenoise just serves static files nicely - we don't lose anything by doing that locally. 2017-11-07 11:50:13 +00:00			`from whitenoise import WhiteNoise`

remove flask-script flask-script has been deprecated by the internal flask.cli module, but making this carries a few changes with it * you should add FLASK_APP=application.py and FLASK_DEBUG=1 to your environment.sh. * instead of using `python app.py runserver`, now you must run `flask run -p 6012`. The -p command is important - the port must be set before the config is loaded, so that it can live reload nicely. (https://github.com/pallets/flask/issues/2113#issuecomment-268014481) * find available commands by just running `flask`. * run them using flask. eg `flask list_routes` * define new tasks by giving them the decorator `@app.cli.command('task-name')`. Task name isn't needed if it's just the same as the function name. Alternatively, if app isn't available in the current scope, you can invoke the decorator directly, as seen in app/commands.py 2017-11-06 13:07:21 +00:00			`from app import create_app`

remove wsgi.py - always serve with whitenoise We're now running our app as a wsgi app locally, so don't need to distinguish between the two processes by having wsgi and application.py whitenoise just serves static files nicely - we don't lose anything by doing that locally. 2017-11-07 11:50:13 +00:00			`PROJECT_ROOT = os.path.dirname(os.path.abspath(__file__))`
			`STATIC_ROOT = os.path.join(PROJECT_ROOT, 'app', 'static')`
			`STATIC_URL = 'static/'`

Expose `application` as a variable This is what Gunicorn is looking for when it’s running the app. Renaming this variable to `app` has caused the app to break once deployed on PaaS. This commit also renames `app` to `flask_app` to make it clear which app is wrapping which other app. 2018-11-29 14:02:20 +00:00			`flask_app = Flask('app')`
remove flask-script flask-script has been deprecated by the internal flask.cli module, but making this carries a few changes with it * you should add FLASK_APP=application.py and FLASK_DEBUG=1 to your environment.sh. * instead of using `python app.py runserver`, now you must run `flask run -p 6012`. The -p command is important - the port must be set before the config is loaded, so that it can live reload nicely. (https://github.com/pallets/flask/issues/2113#issuecomment-268014481) * find available commands by just running `flask`. * run them using flask. eg `flask list_routes` * define new tasks by giving them the decorator `@app.cli.command('task-name')`. Task name isn't needed if it's just the same as the function name. Alternatively, if app isn't available in the current scope, you can invoke the decorator directly, as seen in app/commands.py 2017-11-06 13:07:21 +00:00
Expose `application` as a variable This is what Gunicorn is looking for when it’s running the app. Renaming this variable to `app` has caused the app to break once deployed on PaaS. This commit also renames `app` to `flask_app` to make it clear which app is wrapping which other app. 2018-11-29 14:02:20 +00:00			`create_app(flask_app)`

			`application = WhiteNoise(flask_app.wsgi_app, STATIC_ROOT, STATIC_URL, max_age=WhiteNoise.FOREVER)`