From 0aeab72431352a4c82c19f57c9300543433a4cf1 Mon Sep 17 00:00:00 2001 From: Aaron Meurer Date: Sat, 11 Feb 2012 22:59:00 -0700 Subject: [PATCH] Add some info on how to use versions in the README --- README.rst | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/README.rst b/README.rst index f091aed..3fc7c5b 100644 --- a/README.rst +++ b/README.rst @@ -70,6 +70,12 @@ should see GUI of SymPy Online Shell. Uploading to GAE ---------------- +Before uploading, you need to update the version. Edit app.yaml, and bump the +version number up by one, and commit this change. Then, go to +https://appengine.google.com/deployment?app_id=sympy-live and delete the +oldest version (we can only have ten versions at once, so if you don't do +this, it will reject the upload). Then, you can upload the new version. + Assuming that sympy-live works properly (also across different mainstream web browsers), you can upload your changes to Google App Engine:: @@ -86,6 +92,20 @@ application and make appropriate changes to ``app.yaml`` (replace in the first line sympy-live with the name of your application). Then you can use ``appcfg.py`` as above, to upload to GAE. +Go to http://.sympy-live.appspot.com (for example, for +version 21, go to http://21.sympy-live.appspot.com/) after uploading and make +sure that everything works. If it does, go to +https://appengine.google.com/deployment?app_id=sympy-live and set the newest +version to the default. + +Changing the version before each upload makes it easy to rollback accidental +regressions. Just go to the dashboard and revert to the latest version that +doesn't have the problem. This also lets you test the latest version after +uploading before deploying it to the main site. + +Do not use versions to upload tests. If you want to test something, create a +separate test app on the App Engine and upload it there. + Development notes -----------------