You can also just have your script prompt for a version control commit each time you update via appcfg. To me, handling the backups on the server side clearly makes the most sense. Amazon's Elastic Block Store and snapshots are godsend for this.
-Adam On Nov 21, 2:46 am, Sylvain <[EMAIL PROTECTED]> wrote: > To backup my code, I upload the sources with 7zip while updating. > > http://groups.google.com/group/google-appengine/browse_frm/thread/4f2... > > Very easy. > > Regards > > On 21 nov, 11:22, Greg <[EMAIL PROTECTED]> wrote: > > > > ( yeah, i now have 10KKK backs up of my pc. ) > > > Now you know why experienced developers are so paranoid about backups. > > I'm sorry about your project - renegotiating the delivery date and > > rebuilding it from scratch will cost you credibility, time, and > > pride. But you have learned a lesson that is more valuable than all of > > that. > > > It's too late to help you, but please, all you other guys that don't > > have backups of your code - DO IT NOW. No, not after the next coffee, > > NOW. And get into the habit of taking a copy home on a flash drive > > every night, just in case. > > > That way we won't be reading your plaintive message asking how to get > > your code back next week. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
