Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(198)

Side by Side Diff: appengine/monorail/README.md

Issue 1868553004: Open Source Monorail (Closed) Base URL: https://chromium.googlesource.com/infra/infra.git@master
Patch Set: Rebase Created 4 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « appengine/monorail/Makefile ('k') | appengine/monorail/app.yaml » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 # Monorail 1 # Monorail Issue Tracker
2 2
3 [bugs.chromium.org](https://bugs.chromium.org) 3 Monorail is the Issue Tracker used by the Chromium project and other related
4 projects. It is hosted at [bugs.chromium.org](https://bugs.chromium.org).
4 5
5 Monorail is the issue tracking tool for chromium-related projects, which is a po rt of the Google Code issue tracker to AppEngine. 6 If you wish to file a bug against Monorail itself, please do so in our
7 [self-hosting tracker](https://bugs.chromium.org/p/monorail/issues/entry).
8 We also discuss development of Monorail at `infra-dev@chromium.org`.
6 9
10 ## Testing
7 11
8 * [API](doc/api.md) 12 In order to run all of the Monorail unit tests, run `make test` in this
13 directory. If you wish to run just a subset of the tests, you can invoke the
14 test runner directly and give it a subdirectory: `../../test.py
15 appengine/monorail/tracker`.
16
17 ## Running Locally
18
19 To run the app locally, you need to have a local MySQL database. Install MySQL
20 according to the canonical instructions for your platform. Then create
21 a new database an import our schema:
22
23 mysql> create database monorail;
24 mysql> source /path/to/infra/appengine/monorail/sql/framework.sql;
25 mysql> source /path/to/infra/appengine/monorail/sql/project.sql;
26 mysql> source /path/to/infra/appengine/monorail/sql/tracker.sql;
27 mysql> exit;
28
29 Then you can run the development server locally with just `make serve`.
30
31 ## Deploying
32
33 The `app.yaml` and `Makefile` files contained in this directory point at the
34 official instances of Monorail maintained by the Chromium Infrastructure Team.
35 If you wish (and have sufficient permissions) to deploy to one of those, simply
36 run `make deploy_staging` or `make deploy_prod`. If you wish to set up your
37 own instance, edit the first line of the `app.yaml` and use gae.py directly,
38 or edit the `Makefile` to add an entry for your AppEngine app ID. It is likely
39 that you'll also want to edit many of the values in `settings.py`, which
40 specify debug email addresses, instance counts, and default Google Storage
41 buckets.
OLDNEW
« no previous file with comments | « appengine/monorail/Makefile ('k') | appengine/monorail/app.yaml » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698