Closed ryanpitts closed 11 years ago
All this has been merged to dev, and tested there by Erin, Dan and Erika. Ready for live, with a couple of important notes.
We need to run the category migration one more time, to pick up any articles that have been added since last week:
python manage.py migrate_article_categories
Now that GitHub data will be stored locally, we need to run these three commands right after deployment:
python manage.py update_code_github_stats
python manage.py update_person_github_stats
python manage.py update_organization_github_stats
Those will fetch the initial data that the templates need in order to display GitHub info.
And then as soon as is reasonable, we should put those three GitHub commands (as well as the Twitter update command) on a cron.
Thanks for the list of tasks to run - very helpful!
Made a few comments for you're attention - shall we deploy this tomorrow morning?
OK, fixes made. Yes, let's deploy in the morning!
All this has been merged to dev, and tested there by Erin, Dan and Erika. Ready for live, with a couple of important notes.
BEFORE DEPLOYMENT
We need to run the category migration one more time, to pick up any articles that have been added since last week:
python manage.py migrate_article_categories
POST DEPLOYMENT
Now that GitHub data will be stored locally, we need to run these three commands right after deployment:
python manage.py update_code_github_stats
python manage.py update_person_github_stats
python manage.py update_organization_github_stats
Those will fetch the initial data that the templates need in order to display GitHub info.
And then as soon as is reasonable, we should put those three GitHub commands (as well as the Twitter update command) on a cron.