Closed friedger closed 10 years ago
Boomerang's all HTML/CSS - you can host this wherever with whatever methodology.
GAE has a push to deploy so it may be worth creating a separate repo / example / wikpage for deployment to various hosting targets but I don't think it's necessarily relevant for this particular repo.
I checked in a version that I configured for GAE (Java) for my chapter. https://github.com/Splaktar/boomerang-gae it was pretty simple. You'll need to change the appengine-web.xml and web.xml to work for your specific app engine project.
Do you guys think it's a good idea to have a python runtine App Engine wrapper for Boomerang? I can provide that.
On Sun, Sep 1, 2013 at 12:40 PM, Michael Prentice notifications@github.comwrote:
I checked in a version that I configured for GAE for my chapter. https://github.com/Splaktar/boomerang-gae it was pretty simple. You'll need to change the appengine-web.xml and web.xml to work for your specific app engine project.
— Reply to this email directly or view it on GitHubhttps://github.com/gdg-x/boomerang/issues/3#issuecomment-23627159 .
as long as its static content... I would go with github pages
This can probably be closed.
Closing this as it is covered here https://github.com/Splaktar/boomerang-gae.
Ideally, I like to git pull from boomerang and from boomerang- and then push to appengine using codenvy.