being able to move out since made specifically for GAE • No generation of views and controllers for admin interface (you have to programmatically generate it yourself)
‘whateverlah’) (person is an object) More info : http://vladimir.orany.cz/everyday%20gaelyk/ 2013/03/17/everyday-gaelyk-simplify-groovlets-flow-by- handling-its-return-value/
groovlets and templates • contribute new URL routes • define and bind new variables in the binding (the "global" variables available in groovlets and templates) • provide any kind of static content, such as JavaScript, HTML, images, etc. • add new libraries (ie. additional JARs) • and more generally, let you do any initialization at the startup of your application
engine related tasks) • ./gradlew appEngineRun (to run locally, accessible with http://localhost:8080) • ./gradlew appEngineStartBackend to deploy to production