Home | History | Annotate | only in /external/chromium/chrome/common/extensions/docs/server
Up to higher level directory
NameDateSize
app.yaml10-Oct-2012144
chromeextensionsdocs.py10-Oct-201214.8K
index.yaml10-Oct-2012482
README10-Oct-20121.6K

README

      1 This directory contains the App Engine server code that hosts the Chrome
      2 Extensions documentation at http://code.google.com/chrome/extensions
      3 
      4 --------------------------------------------------------------------------------
      5 Running the server locally
      6 
      7 1. Install the Python App Engine SDK for your platform:
      8    http://code.google.com/appengine/downloads.html
      9 
     10 2. Use the installed development server to serve the contents of this directory:
     11    http://code.google.com/appengine/docs/python/tools/devserver.html
     12 
     13    Typically, this will be something like (run from this directory)
     14 
     15      /path/to/dev_appserver.py --post=8080 .
     16 
     17 3. Navigate to http://localhost:8080 (or whatever port you specified)
     18 
     19 --------------------------------------------------------------------------------
     20 Deploying the server to code.google.com:
     21 
     22 You will need to have access to the appropriate appspot.com app. Contact
     23 aa (a] chromium.org or kurrik (a] chromium.org to obtain access.
     24 
     25 Once you have access:
     26 
     27 1. Increment the version in app.yaml so we can roll back if the update breaks.
     28 
     29 2. Run appcfg.py (supplied with the App Engine SDK) to upload the server code:
     30 
     31     appcfg.py update .
     32 
     33 3. When prompted for your credentials, enter the information for the account
     34    that has access to the production app.
     35 
     36 4. Go to http://www.appspot.com, select the docs project, click "versions" in
     37    the sidebar, and make the version you just deployed the "default" version.
     38 
     39    If you get an error about too many versions when deploying, go into this
     40    view and delete the version which was deployed the longest time ago.  Then
     41    try to deploy again.
     42 
     43