boodebr sandbox App Engine samples and tutorials from boodebr.org Sun, 03 Aug 2008 13:36:00 +0000 WikklyText 1.3.4-WIP http://blogs.law.harvard.edu/tech/rss InstallSdk InstallSdk.html
  • Install Python 2.5 if you don't already have it.
  • Install the AppEngine SDK (last tested with version 1.1.1)
    You do not need a Google App Engine account to begin developing and running your own apps locally.

    • blog comments powered by Disqus ]]>     c01b5e02dec16e885ac7c61faf13c0ec2463db31 Sun, 03 Aug 2008 13:36:00 +0000     Welcome Welcome.html Google's App Engine platform. My primary focus will be on building applications using the low-level features of the App Engine API, not a prebuilt framework. This site is very much a work in progress. If you'd like to keep up to date on the latest changes as it grows, subscribe to the RSS feed

    You can now leave comments on most pages. This is an experimental feature.


    Tutorials:
    • AccountSetup: A walkthrough of setting up your AppEngine account.
    • InstallSdk: Setup your local machine with the AppEngine development environment.
    • StaticContent: Lets get started with some nice static content.
    • HelloWorld: The simplest possible AppEngine application
    • EnvironmentInfo: A verbose look at the information we receive from the CGI environment.
    • LoginDemo: An example of letting a user login (with their Google account) and storing some persistent data for the user.
    • UrlDemo: A demo of handling URLs and query strings.
    • SessionDemo: A demo of session handling. Completely independent of user logins so works for guest users as well as those with Google accounts.
    ]]>     c0a2ed799374160351b50c9c5bda5ebaeb8b9d73 Fri, 18 Jul 2008 01:00:00 +0000     LoginDemo LoginDemo.html Users API. This API allows users to login to your website with their Google account. The demo shows two basic ideas:
    • Allowing a user to login and logout
    • Storing some data along with the user, as you would do in a typical application.

    View the demo here and the source code.

    blog comments powered by Disqus ]]>     397e9006115e301c64b28154ae230bb3242bd730 Fri, 18 Jul 2008 00:58:00 +0000     HelloWorld HelloWorld.html AppEngine!

    Create hello/hello.py:
    # straight out of PEP 333 (http://www.python.org/dev/peps/pep-0333/)
    def simple_app(environ, start_response):
        "Simplest possible application object"
        status = '200 OK'
        response_headers = [('Content-type','text/plain')]
        start_response(status, response_headers)
        return ['Hello from CGI Handler!\n']

    # does not know nor care that it is running under AppEngine!
    from wsgiref.handlers import CGIHandler
    CGIHandler().run(simple_app)


    Update app.yaml and add:
    - url: /hello.*
      script: hello/hello.py


    Now try it out: http://boodebr.appspot.com/hello

    Notice our simple application does not care what URL you pass to it, it always gives the sample result. For example: http://boodebr.appspot.com/hello/a/b/c?q=123&z=789



    blog comments powered by Disqus ]]>     986a7c95caf600a4ef0e0cb01b301cdef9efd7ac Fri, 18 Jul 2008 00:58:00 +0000     SessionDemo SessionDemo.html
  • Generate a session key for each new visitor.
  • Store session key in a cookie named "short-cookie".
  • Use the session key to load/store some user-specific data using the AppEngine memcache.

    • For this demo, both the cookie and session data are set to expire in 60 seconds so you can see what happens.

    View the demo: http://boodebr.appspot.com/sessdemo (source code)

    blog comments powered by Disqus ]]>     5bfb44dd0d80a074b49a44c565b43aa2b6cd0a0e Fri, 18 Jul 2008 00:57:00 +0000     StaticContent StaticContent.html
    On my laptop, my development directory is c:\frank\src\gapp_boodebr. I'll refer to this as the toplevel folder for brevity. Under that directory is a folder wiki that holds the wiki content you are viewing now.

    In the toplevel folder, I created app.yaml:
    app.yaml
    application: boodebr
    version: 1
    runtime: python
    api_version: 1

    handlers:
    - url: /wiki
      static_dir: wiki
    The key here is the handlers section where I tell the app engine to treat wiki\ as static content. That's it - no .py files are required.

    To test my app locally, I run:
    cd c:\frank\src\gapp_boodebr
    dev_appserver.py .
    Viewing the results at http://127.0.0.1:8080

    When happy with the results, I upload to App Engine:
    appcfg.py update .


    And voila, there it is: http://boodebr.appspot.com/wiki/index.html

    blog comments powered by Disqus ]]>     53bb0f6757de721d0eb69d76108905e99ee8925b Fri, 18 Jul 2008 00:56:00 +0000     EnvironmentInfo EnvironmentInfo.html
    For this sample, create a new folder envinfo and add envinfo/envinfo.py:
    def env_app(environ, start_response):
        "Show environ verbosely"
        status = '200 OK'
        response_headers = [('Content-type','text/plain')]
        start_response(status, response_headers)
        
        h = 'My environ is a %s\n' % type(environ)
        h += '\nIt contains these key:value pairs:\n\n'
        keys = environ.keys()
        keys.sort()
        for k in keys:
            h += '%s: %s\n' % (k,environ[k])
            
        return [h]

    # does not know nor care that it is running under AppEngine!
    from wsgiref.handlers import CGIHandler
    CGIHandler().run(env_app)


    Add to app.yaml:
    - url: /envinfo.*
      script: envinfo/envinfo.py  


    Try it out: http://boodebr.appspot.com/envinfo

    Notice how PATH_INFO and QUERY_STRING are set when you pass a longer URL:
    http://boodebr.appspot.com/envinfo/a/b/c?qrs=abc+123%09456&tuv=43.234

    blog comments powered by Disqus ]]>     7da8d2f8615b5fa1d3c3cecdd065ba598ca4d545 Fri, 18 Jul 2008 00:56:00 +0000     UrlDemo UrlDemo.html wsgiref.util and cgi modules to parse URLs and query strings. There is nothing specific to AppEngine in this sample.

    Try it on some URLs: Here is the (source code)

    blog comments powered by Disqus ]]>     3d284d4c9aca4663d9e8d431deaa80813c650cdc Fri, 18 Jul 2008 00:55:00 +0000     AccountSetup AccountSetup.html http://appengine.google.com. This will (currently) put you on a waiting list so you won't be able to move to the next step for a while.

    Once your account is created, you'll receive an email from Google. Now when you visit http://appengine.google.com you'll reach the Welcome screen:



    Clicking "Create Application" takes you to this screen:



    Be careful choosing an Application Identifier because you cannot change it. You can change the Application Title later (this is apparently only used when users login). The Check Availability button gives a quick way to see if your desired name is available. I left the Authentication Options set to the default.

    Once you find a name you like and click Save you will see:




    Now whenever you visit http://appengine.google.com you will see your account(s) in the console view:



    That's it! The hardest part is waiting for your account to be activated.

    ]]>     c390c71b153da24bf6f94ab371a05309bbeee5ed Fri, 18 Jul 2008 00:33:00 +0000     InfoDump InfoDump.html
    To create this example, I made a new subfolder infodump/ containing a single file info.py (source code). To hook it into the site, I added the following to app.yaml:
    - url: /infodump.*
      script: infodump/info.py
    Make sure to add this handler before the default handler at the bottom of the file.
    info.py defines two primary methods:
    index()
    This method handles requests for /infodump
    default()
    This handles all other requests.

    Here are two examples. The only difference between them is that in the second example the extra path and query will be shown as args and kwargs in the request table.

    Request for "/info" will be handled by index()
    http://boodebr.appspot.com/infodump

    This request will be handled by default(). Notice that the args and kwargs will now be filled in the table
    http://boodebr.appspot.com/infodump/a/b/c?qA=AAA&qB=BBB
    ]]>     7762e29845c019e96baaa829cf0af255bfac5458 Sun, 06 Jul 2008 19:50:00 +0000     NotFullyWorking NotFullyWorking.html
    Not Working
    I originally started out here using CherryPy. However, I discovered some showstopper issues along the way, so I stopped at least for now and switched to plain WSGI. Feel free to use these demos as a starting point if you wish.
    ]]>     fef9d4c65f3c6334d781a04e18112ec7cfdd1519 Sun, 06 Jul 2008 14:54:00 +0000     AppEngine AppEngine.html App Engine API]]> 6ba225a42b7f782bae6835ded598822728013c13 Sun, 06 Jul 2008 13:49:00 +0000 InstallCherryPy InstallCherryPy.html
  • Download CherryPy (you need at least version 3.1.0)
  • Unpack into your application folder, for example:
    cd c:/frank/src/gapp_boodebr
    tar zxvf ~/CherryPy-3.1.0.tar.gz
  • Use the --prefix option to install to application folder (not system wide):
    cd CherryPy-3.1.0
    python setup.py install --prefix="c:\frank\src\gapp_boodebr"
  • This doesn't place it exactly where I need it, so move it to the toplevel:
    mv ../Lib/site-packages/cherrypy/ ..
  • And cleanup
    cd ..
    rm -rf CherryPy-3.1.0
    • ]]>     3b06fc2b757c1cfe9a1f370b7accfb0d177212af Sat, 05 Jul 2008 23:53:00 +0000     AboutTheseDocs AboutTheseDocs.html WikklyText, a free set of Python wiki tools. Currently, this site is statically rendered offline and uploaded to appspot, instead of being a live wiki server.]]> e8c308abffa49c3f2ea63079a2403890994e469a Sun, 20 Apr 2008 02:50:00 +0000