Google Appengine implementation on Wolfire

[dougnukem]

I'm curious to hear more details about Wolfire's implementation of Google Appengine for their main website and their multiplayer game lobbys.

It sounds like you are using Google Appengine's python applications to act as a "cache" for your main site and blog.

Are you simply using URL redirects from http://wolfire.com to your *.appspot.com appengine address?

What does your python application do, it sounded like you were sucking in the RSS feed from your wordpress blog, which I assume is hosted on your dedicated servers at: http://blog.wolfire.com/? How are you managing the templates on your site and presenting the RSS feed of your wordpress blog?

I'm really curious because I've been thinking about setting up my old game dev blog that used wordpress, and I'd really like to be able to easily support scalability.

[Jeff]

Are you simply using URL redirects from http://wolfire.com to your *.appspot.com appengine address?

No, I wrote the website from scratch using the standard Google App Engine modules.

Most of the site is simple templating, but there are a few parts that are non-trivial, like the server browser or our order system.

The root page (www.wolfire.com) displays our blog by grabbing the RSS when wordpress pings it and stores it in memcache.

Let me know if you have any specific questions!

[Lord_of_Sausage]

You know nothing about HTMl! Its all just from John and his beard. It uses a mega-drive reciver from their serverbrowser, and gains awesome (over)growth, through David and Aubrey's shoes.

Thats how it works...


Oh, and i just got the best John's beard joke ever!
"I really hope john's beard will overgrowth back again"... ya, its kinda bad...