This app can be run completely using Docker
and docker-compose
. Using Docker is recommended, as it guarantees the application is run using compatible versions of Python and Node.
There are three main services:
To run the development version of the app
docker-compose up flask-dev
To run the production version of the app
docker-compose up flask-prod
The list of environment:
variables in the docker-compose.yml
file takes precedence over any variables specified in .env
.
Run the following commands to bootstrap your environment if you are unable to run the application using Docker
cd poetry-similarity-app
pip install -r requirements/dev.txt
npm install
npm run-script build
npm start # run the webpack dev server and flask server using concurrently
You will see a pretty welcome screen.
When using Docker, reasonable production defaults are set in docker-compose.yml
FLASK_ENV=production
FLASK_DEBUG=0
GUNICORN_WORKERS: 4
ES_HOST: http://62.204.199.252
ES_PORT: 9200
Therefore, starting the app in "production" mode is as simple as
docker-compose up flask-prod
If running without Docker
export FLASK_ENV=production
export FLASK_DEBUG=0
export ES_HOST=<elasticsearch_server>
export ES_PORT=9200 # elasticsearch port
npm run build # build assets with webpack
flask run # start the flask server
To run all tests, run
docker-compose run --rm manage test
flask test # If running locally without Docker
To run the linter, run
docker-compose run --rm manage lint
flask lint # If running locally without Docker
The lint
command will attempt to fix any linting/style errors in the code. If you only want to know if the code will pass CI and do not wish for the linter to make changes, add the --check
argument.
Files placed inside the assets
directory and its subdirectories
(excluding js
and css
) will be copied by webpack's
file-loader
into the static/build
directory. In production, the plugin
Flask-Static-Digest
zips the webpack content and tags them with a MD5 hash.
As a result, you must use the static_url_for
function when including static content,
as it resolves the correct file name, including the MD5 hash.
For example
<link rel="shortcut icon" href="{{ "{{" }}static_url_for('static', filename='build/img/favicon.ico') {{ "}}" }}">
If all of your static files are managed this way, then their filenames will change whenever their
contents do, and you can ask Flask to tell web browsers that they
should cache all your assets forever by including the following line
in .env
:
SEND_FILE_MAX_AGE_DEFAULT=31556926 # one year