Besides fixing dependency issues and a failing test, I added an environment variable $FLASK_ENV which controls how the docker container serves the app.
When $FLASK_ENV == production, serve the app using uwsgi. You must configure the port in uwsgi.ini.
When $FLASK_ENV == development, serve the app with flask's built in http server
When $FLASK_ENV == development-expose, serve the app with flask's built in http server and setup a tunnel with ngrok so twilio integration works. The app must be accessed through the tunnel in this case (a link is printed to the console).
vbrown608
commented
8 years ago
This branch merges in master from spacedogXYZ/call-power and includes fixes I had to make to get the docker build working. You can see all the added changes on top of the merge at https://github.com/EFForg/call-congress/compare/e1f0e91...EFForg:upgrade.
Besides fixing dependency issues and a failing test, I added an environment variable
$FLASK_ENVwhich controls how the docker container serves the app.$FLASK_ENV == production, serve the app using uwsgi. You must configure the port inuwsgi.ini.$FLASK_ENV == development, serve the app with flask's built in http server$FLASK_ENV == development-expose, serve the app with flask's built in http server and setup a tunnel withngrokso twilio integration works. The app must be accessed through the tunnel in this case (a link is printed to the console).