There are no post-deploy hooks, but you can probably wrap the deploy script to invoke a handler that fires off a job that does what you need.
-- Ikai Lan Developer Programs Engineer, Google App Engine Blogger: http://googleappengine.blogspot.com Reddit: http://www.reddit.com/r/appengine Twitter: http://twitter.com/app_engine On Wed, Feb 9, 2011 at 10:02 AM, Peter Warren <pe...@treehouselogic.com>wrote: > Is there a way to execute code on a new appengine deploy but not on a > load of a fresh app instance due to reasons other than a new deploy? > > I would like our appengine instance to process a bunch of files on a > new deploy, but not any other time. Is there a good way to do this? > Obviously processing the files and then deleting them would work, but > as far as I know appengine doesn't allow modifying the deployed > files. Something like setting a flag in the datastore would work, but > I would need that flag to be automatically reset on a new deploy. > > Any ideas? > > Thanks, > Peter > > -- > 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. > > -- 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.
