OLD | NEW |
(Empty) | |
| 1 Developing an appengine application |
| 2 =================================== |
| 3 |
| 4 Structure in infra.git |
| 5 ---------------------- |
| 6 |
| 7 Infra.git hosts several google AppEngine projects, located in the ``appengine/`` |
| 8 directory. Each subdirectory of ``appengine/`` is supposed to be a single |
| 9 AppEngine application. Code shared between applications should live in |
| 10 ``appengine_modules/`` and be symlinked into application directories (the |
| 11 AppEngine upload script ``appcfg.py`` follows symbolic links). |
| 12 |
| 13 |
| 14 Testing of AppEngine applications |
| 15 --------------------------------- |
| 16 Tests included in AppEngine applications (classes deriving from |
| 17 ``unittest.TestCase``) are run by ``test.py``. Some convenience functions to |
| 18 help using the testbed server are included in |
| 19 ``appengine_modules/testing_utils``. Some examples can be found in existing |
| 20 applications. |
| 21 |
| 22 |
| 23 Managing AppEngine apps |
| 24 ----------------------- |
| 25 A convenience script wrapping ``appcfg.py`` called ``gae.py`` can be used to |
| 26 simplify and normalize the deployment process in ``infra.git``. Just add a |
| 27 symlink to it in your application. It is located in |
| 28 ``appengine/swarming/appengine/components/tools/gae.py``, but this location is |
| 29 bound to change soon(c) (2014-12-05). |
| 30 |
OLD | NEW |