-
Notifications
You must be signed in to change notification settings - Fork 1
Deployment Steps
STOP! Have you fully tested the code in stable on your local GAE test site? If not, go away and do so.
-
Switch to the STABLE branch - git checkout stable
-
Make sure your branch is up-to-date - git pull origin stable
-
Open util/consts.py. Scroll to the bottom of the file. Ensure that local_consts are commented off.
-
In your browser, open up the GAE admin panel to Versions.
-
Open up app.yaml. Application should be 'social-referral'. Version should be 1 larger than the current live version. ie. if you are using 7-56 in the GAE Admin Panel, your app.yaml should say 7-57.
-
DEPLOY! Watch the logs to make sure it all worked properly. If GAE complains that you've reached the max # of versions, go into the GAE Admin Panel and delete the oldest version. Redeploy.
-
Your code isn't live - take a break and relax.
-
Ready to turn it on? Refresh your Version page and turn it on.
-
Watch the error logs to see if anything breaks. If it does, switch back to the older Version IMMEDIATELY. Test the new code by visiting a few live sites and playing with the widget. Check error logs. If it looks good, keep the error logs open in a tab and check back every few minutes for edge cases.
-
Pat yourself on the back. Deployment done.
Our version numbers follow this format majorVersion-minorVersion. Whenever you release a new feature or major change, increase the majorVersion number (minorVersion will go to 0 to star tcounting up again).