April 9th, 2008 · Posted by Mark Luffel ·

Running Appcelerator on the Google App Engine

We know you’re excited about Google’s App Engine. How can you help it? If the opportunity to run your apps on a 20,000 terabyte per day cloud computer isn’t enough, certainly the ability to run Python on that cloud must be!

We were excited too, we admit. So yesterday we started porting our existing python server-side code to the App Engine, and today we’re releasing it through our developer network. This afternoon we ported Tejus’s appTunes demo to the App Engine and deployed it at http://apptunes.appspot.com.

So, how can you be incredibly hip too?

First, download and install Python 2.5, the App Engine SDK, and the Appcelerator SDK.

Now, make yourself a project and launch it locally (replacing myapp with your project’s name)

1
2
3
app create:project . myapp appengine
cd myapp
app run:project

If this is your first time on the developer network, you’ll need to enter your login.

If everything installed correctly you will see a bunch of logging info ending with:

1
Running application myapp on port 8080: http://localhost:8080

Like the other Appcelerator backends, you can find your message handlers in app/services/. So, go digest the App Engine documentation and write something great. Once you’re ready to send your app to the cloud just run:

1
app deploy:project

This will ask you for your App Engine account info, and then upload your project.

We’re putting together a screencast of this, and now that I’ve finished futzing with Windows command-line problems for this integration, maybe I’ll get some time to learn the Datastore API.

And now, a message from our sponsors:

In the spirit of open source and shared learning, we’d like to acknowledge a few key pieces that we put together to make this demo application that Tejus built happen:

  • Doug McCune for his super bad ass CoverFlow Flex Component. We’ve used the Appcelerator Widget API to widgetize this flex widget and allow it to be both declaratively added to markup and the power of Appcelerator’s Web Expression Language to add remoting capabilities for data binding. This also shows off the power of using Appcelerator + Adobe’s Flex bridge to get the best of both worlds.
  • JS Sound Kit for the streaming audio for playing the MP3s. Again, we built this as a reusable widget.
  • Jamendo and the independent artists for the awesome, DRM-free music and cool looking coverart.

Tech Tags:

Popularity: 40% [?]

Tags: Announcement · Product Updates

6 Responses to “Running Appcelerator on the Google App Engine”

  1. Open Source mobile edition Says:

    […] what Appcelerator is offering. The Atlanta-based Java tools outfit is porting its software over via its developer network, and […]

  2. Build RIA applications and deploy to Google AppEngine Says:

    […] Friday we announced support for Appcelerator RIA + Google AppEngine. This means you can build rich Internet applications using Appcelerator and then deploy them into […]

  3. Ajaxian » Appcelerator on App Engine Says:

    […] had a funny feeling that we would see frameworks and tools starting to support Google App Engine. Appcelerator has added support into their SDK, so you can now create an App Engine […]

  4. Introducing Appcelerator 2.1 Says:

    […] is a natural fit for serving as the RIA + SOA part of the cloud computing stack. Check out our blog post to learn more about how to use Appcelerator on […]

  5. Nickelstar Says:

    This article contains a small error that will prevent the web application from running locally (at least on my Mac!). The application name should not contain an underscore in the name. If it does have an underscore, an error will be thrown that indicates there is a pattern matching problem in the application name. To fix I simply renamed my_app to myapp and everything worked great. BTW, thanks for the article… this looks to be an exciting combination of technologies. Keep up the great work!

  6. Mark Luffel Says:

    Thanks for the feedback, I changed the name so that people don’t get tripped up on that.

Leave a Reply