On Fri, Mar 23, 2012 at 12:29 PM, Jim Washington <[email protected]> wrote: > Hi, all > > I've been playing around with making it easy for me to use the > combination of the subject apps. > > Tom Willis, on the pylons-discuss mailing list, proffered the idea of > using the pyramid scaffold engine to create an initial file structure > for a pyramid app that is managed by buildout for easy and proper > uploading to Google App Engine. And there's code: > > https://github.com/twillis/pyramid_appengine > > It's in fairly early development but serviceable right now. > > I'm getting a real charge out of buildout, though. I can drop one or > more example pyjamas app folders into my pyramid app's 'clients' folder > and have buildout rebuild them all with the same args, optionally > zapping the static/lib directory first, and put their output in the > pyramid app's static folder. Then I can have buildout pull that static > folder out of the pyramid app's distribution for GAE so that GAE can > serve it all statically. The point is eventually to have multiple > pyjamas front-ends to my backend data store.
yyyeahhhh.... > If there is any interest, I could probably fork Tom Willis's stuff and > make a scaffold starter for this particular setup. yes please. i've been meaning to play with gae, i have a need for it in a couple of cases, but the barrier to entry for me has been the amount of arseing about needed. if there's a straightforward way to just put in some parameters (3 or 4) into a config file, hit "compile" and it's done, i'll be a really happy bunny. l.
