I have a "deploy" script that generates and minifies my client side code, CSS, and various other pages before calling appcfg to deploy a new version - some of these generated files are scripts that run on the server, others are static files that will be requested by the browser.
I previously posted a note about the outer wrapper (that checks source code etc) on stackoverflow http://stackoverflow.com/questions/4374659/app-engine-launching-a-script-upon-update-run/4880481#4880481 That post doesn't include details of the step that does the actual generation, but yeah, I have a few "static data" things that I don't bother storing in the database and are instead persisted via generated files, and then because I know my source code change number at the time of deployment, then, for example, the generated mainpage and other scripts always append a cache busting version number, so I can have a long expiration time in app.yaml on everything but the short main page itself (type attributes removed for clarity below) <link rel="stylesheet" href="/css/myapp.css?r=987 " /> <script> var MyApp = {}; MyApp.version = 987; MyApp.loadJs = function(href,async,appendVer) { }; </script> <script src='myapp.js?r=987'/> I have a corresponding "run" script that calls the same generate script but with different options to make a main page that pulls in all the individual files rather than the minified version etc and generates a random dev version key ("dev$RANDOM") and then calls dev_appserver. Is that the sort of thing you meant ? -- T -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. 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.
