~within the machine, run livebloglog~ ideally, but this isn't working on the production machine right now, and I can't find this command in the repo
tail -f /var/log/liveblog/deploy.log
to run locally, use liveblog virtualenv, run mongod, fab daemons.main, and fab app:7777
to deploy new code to production, run fab production master deploy, and restart the production daemon with fab production servers.restart_service:deploy
to run locally, use docker-compose up daemon; don't forget that you may need to docker-compose up bootstrap_db beforehand if you're making a schema or metadata change
to deploy new code to production, run fab production master servers.checkout_latest, and restart the production daemon with fab production servers.restart_service:fetch_and_publish_results
a similar warning as above that you may need to run bootstrap_db after deploying code and before restarting the daemon if you're making a schema or metadata change; right now, fab production master servers.fabcast:data.bootstrap_db is broken, so you have to ssh in, source ~/apps/elections18_general/virtualenv/bin/activate, and then cd ~/apps/elections18_general/repository/ && fab data.bootstrap_db
Admin panel
ssh ubuntu@52.90.111.124
tail -f /var/log/elections18_general/uwsgi.log will show all traffic to the uWSGI app
tail -f /var/log/elections18_general/admin_app.log will show the Python/Flask errors
to run locally, use docker-compose up app
to deploy new code to production, run fab production master servers.checkout_latest; the uwsgi app should respond to these changes next time you load an admin-panel webpage
Running list:
Liveblog
ssh ubuntu@18.210.214.159
livebloglog
~ ideally, but this isn't working on the production machine right now, and I can't find this command in the repotail -f /var/log/liveblog/deploy.log
liveblog
virtualenv, runmongod
,fab daemons.main
, andfab app:7777
fab production master deploy
, and restart the production daemon withfab production servers.restart_service:deploy
Data pipeline
ssh ubuntu@52.90.111.124
tail -f /var/log/elections18_general/fetch_and_publish_results.log
docker-compose up daemon
; don't forget that you may need todocker-compose up bootstrap_db
beforehand if you're making a schema or metadata changefab production master servers.checkout_latest
, and restart the production daemon withfab production servers.restart_service:fetch_and_publish_results
bootstrap_db
after deploying code and before restarting the daemon if you're making a schema or metadata change; right now,fab production master servers.fabcast:data.bootstrap_db
is broken, so you have tossh
in,source ~/apps/elections18_general/virtualenv/bin/activate
, and thencd ~/apps/elections18_general/repository/ && fab data.bootstrap_db
Admin panel
ssh ubuntu@52.90.111.124
tail -f /var/log/elections18_general/uwsgi.log
will show all traffic to the uWSGI apptail -f /var/log/elections18_general/admin_app.log
will show the Python/Flask errorsdocker-compose up app
fab production master servers.checkout_latest
; theuwsgi
app should respond to these changes next time you load an admin-panel webpageGraphics
apps.npr.org
distribution to check rates of error responses, and total hits over timefab app
fab production master deploy