对于Mac用户:Google App Engine Launcher会将这些命令包含在程序当中,你可以将这些命令添加到命令path通过选择'GoogleAppEngineLauncher'菜单里的“Mak Symlinks.”。或者,你可以直接用Launcher来运行开发服务器以及展示你的网页程序。. Start the Google App Engine Launcher. Open the Google App Engine Launcher application (logo on right) The first time you start the Launcher on Mac, you may see a dialog box asking you about symbolic links. For Google App Engine to work, you must agree to set up symbolic links. Register your app with Google App Engine. Next you need to specify your Google App Engine directory. If you are on a Windows machine and you used the default location it will be here: C: Program Files (x86) Google googleappengine. For a Mac the Google App Engine directory is here: /usr/local/googleappengine. Then is will display a list of Python libraries available for this project. Google; About Google; Privacy; Terms.

Prerequisites:
  1. For developing on GAE using Python run-time you will need to install first the Python run-time in your local machine. You can find the binary installers for Windows, Linux and Mac at
    http://www.python.org/download/
    Note: For windows users you must use the correct Python installer depending if you have a 64-bit or a 32-bit Windows version. Follow this simple guide from Yahoo Answers to check which one is best for you:
    Windows Vista
    Method 1
    1. Click Start, type system in the Start Search box, and then click system in the Programs list.
    2. The operating system appears as follows:
    • For a 64-bit version operating system: 64-bit Operating System appears for the System type under System.
    • For a 32-bit version operating system: 32-bit Operating System appears for the System type under System.
    Method 2
    1. Click Start, type system in the Start Search box, and then click System Information in the Programs list.
    2. The operating system appears as follows:
    • For a 64-bit version operating system: x64-based PC appears for the System type under Item.
    • For a 32-bit version operating system: x86-based PC appears for the System type under Item.

    Microsoft Windows XP Professional
    Method 1
    1. Click Start, click Run, type sysdm.cpl, and then click OK.
    2. Click the General tab. The operating system appears as follows:
    • For a 64-bit version operating system: Microsoft Windows XP Professional x64 Edition Version < Year> appears under System.
    • For a 32-bit version operating system: Microsoft Windows XP Professional Version< Year> appears under System.
    Note <Year> is a placeholder for a year.
    Method 2
    1. Click Start, click Run, type winmsd.exe, and then click OK.
    2. In the details pane, locate Processor under Item. Note the value.
    • If the value that corresponds to Processor starts with x86, the computer is running a 32-bit version of the Windows operating system.
    • If the value that corresponds to Processor starts with ia64 or AMD64, the computer is running a 64-bit version of the Windows operating system.

    Microsoft Windows Server 2003
    Method 1
    1. Click Start, click Run, type sysdm.cpl, and then click OK.
    2. Click the General tab. The operating system appears as follows:
    • For a 64-bit version operating system: Microsoft Windows Server 2003 Enterprise x64 Edition appears under System.
    • For a 32-bit version operating system: Microsoft Windows Server 2003 Enterprise Edition appears under System.
    Method 2
    1. Click Start, click Run, type winmsd.exe, and then click OK.
    2. In the details pane, locate Processor under Item. Note the value.
    • If the value that corresponds to Processor starts with x86, the computer is running a 32-bit version of the Windows operating system.
    • If the value that corresponds to Processor starts with EM64T or ia64, the computer is running a 64-bit version of the Windows operating system.

    Finally, Intel Itanium-based computers can only run 64-bit versions of Windows. Intel Itanium-based computers cannot run a 32-bit Windows operating system. Currently, 64-bit versions of Windows only run on Itanium-based computers and AMD64-based computers.
    Note: For Linux users you must also check if you are using a 64-bit or 32-bit kernel by issuing as root the shell command 'uname -m' without quotes.
  2. For developing on GAE using Java run-time you need to install first the Java SE run-time edition (JRE). Most windows machines already comes with Java installed but its best to get the latest JRE and the Java SDK as well from http://java.sun.com/javase/downloads/index.jsp which contains all the installers for Windows and Linux. Mac users can get ti directly from the official Apple developer site at http://developer.apple.com/java/download/
    Note: There are two versions of Java, namely the Standard Edition (SE) and the Enterprise Edition (EE). I would recommend using SE and here is difference as explained on DevShed forums between two editions:
    'Enterprise edition is largely web based applications. Servlets, JSPs, Java Beans, etc. You can put a swing or applet front on a j2ee application but the bulk of the application is still going to be something server based that a bunch of people have to connect to.
    J2SE is mostly for local applications that don't require enterprise servers behind them.'

    Note: Linux users can follow the guide from Sun on how to install Java found at http://java.com/en/download/help/5000010500.xml while for specific distributions check this list:
    • For Ubuntu: https://help.ubuntu.com/community/Java
    • For CentOs, RedHat and Fedora: http://www.sysadmin.md/install-java-on-centos-redhat-fedora.html
    Note: For Linux users you must also check if you are using a 64-bit or 32-bit kernel by issuing as root the command 'uname -m' without quotes.
Installing the GAE SDK:

  1. Download the Google App Engine SDK, you can find both the GAE Python run-time and Java (early look) run-time SDKs at http://code.google.com/appengine/downloads.html
    Note: For Mac users, the SDK and Launcher is included in the single .dmg package.
  2. Run the downloaded installer, if you have performed the prerequisite steps properly the installer will be able to detect the Python or Java SE run-time installed, if not; it will prompt you to install them first.
  3. For Windows users you can download the Unofficial GoogleAppEngineLauncher for Windows at http://code.google.com/p/gaelwin/
  4. Congratulations, you are now ready to start writing your first Google App Engine application. Check the Table of Contents to find out what you can do next.
Google launcher app for android

Google App Engine Launcher Program

As recently announced on the Google App Engine Blog, the 1.2.5 SDK for Python now includes a GUI for creating, running, and deploying App Engine applications when developing on Windows. We call this the Google App Engine Launcher.

About a year ago, a few of us recognized a need for a client tool to help with App Engine development. In our 20% time, a we wrote a launcher for the Mac. Of course, not all App Engine developers have Macs, so more work was needed. Thus, a new crew of 20%ers set off to write a launcher for our App Engine developers on Windows. Although Google is spread out across many offices around the world, it is surprisingly easy to connect with passionate engineers. For example, this new launcher for Windows has contributions from Dave Symonds in Australia, Mark Dalrymple on the east coast, and more engineers here in Mountain View.

The Windows launcher is written in Python and uses wxPython for its GUI. This means (with a little care) the launcher should work on Linux, and we'd like Linux developers to have the option of using it. Although we ship a binary of the Launcher for Windows (thanks to py2exe), shipping binaries for Linux is a bit more challenging. Fortunately, Google has a well-traveled path for solving this problem. For example, Google O3D provides binaries for Windows/Mac; it also provides source code and instructions for building on Linux. Thus inspired, we've open sourced the Windows launcher so that developers can use it on other platforms.

The goal of the launcher is to help make App Engine development quick and easy. There may be other tasks you'd like to integrate (e.g. run tests, re-encode images before deploying, etc) and with the launcher now open sourced, you can add them! We look forward to seeing contributions from the community.

We have also started the process of open sourcing the Mac version of the launcher. The source code is now available; however, it references some missing Google libraries, so it won't yet compile in its current state. Fortunately, those libraries have also been open sourced, so it will be possible to get things up and running using entirely open source code. I'll be using more of my 20% time to clean up the Mac launcher project in the coming weeks.

We hope the launcher will improve the workflow for App Engine developers. We also hope the source code will enable developers to adapt it to their needs, just as we do on Chrome, my main project. Finally, I am proud to continue a tradition of openness which began with my very first project at Google.

Google App Engine Launcher Download

-- John Grabowski, Software Engineer

Let us know how the launcher works for you.

Google App Engine Launcher Machine Shops

Open Source Code for the App Engine Launcher: for Windows and Linux, and for Mac OS X.