I use git for controlling my App Engine source code. ( For example, I released my early attempt at a blog over at http://github.com/DocSavage/bloog )
When you deploy on App Engine, you can set the version ID of your code. I've created a shell script which automatically generates the git version hash and puts it in the app.yaml "version" key/value. App Engine will let you use any alphanumeric string for versions, so git hashes are OK. So your team can use whatever source control system for the code (git is great for distributed teams), and when you deploy, you have multiple versions of your app in the cloud ready to run. Each version's ID tells you the exact repository state. The App Engine server console lets you easily switch the app version used for your main url, and it even lets you test each version separately through longer urls at appspot.com. The system is pretty nice. -Bill On Jan 22, 5:33 pm, GenghisOne <mdkach...@gmail.com> wrote: > Does the current version of Google's App Engine vision address > distributed software development and source control? > > Or put more practically, how can a couple of distributed software > developers collaborate on a Google App? For instance, how can I pull > down the latest source and update it? > > Thx. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
