Gitiles
Code Review Sign In
gerrit.avm99963.com / monorail-avm99963 / refs/heads/main
commit097a82454a55c404f9def0e27e01f05dbc23689f[log] [tgz]
authorAdrià Vilanova Martínez <me@avm99963.com>Fri Jan 26 21:20:10 2024 +0100
committergerritbot <gerritbot@avm99963.com>Fri Jan 26 21:40:45 2024 +0100
tree352ade293a9fa64110eac5311a89a840a0611a98
parent5ccb1a024483c6c54beec4f86fc92541cbf1fa2c [diff]
Add missing staging settings

In the local environment Monorail is now ran with the staging
configuration. This fixes it.

GitOrigin-RevId: f2cdf35c33a8b956a038287fc972b97e918d1bf9
1 file changed
tree: 352ade293a9fa64110eac5311a89a840a0611a98
  1. api/
  2. businesslogic/
  3. doc/
  4. features/
  5. framework/
  6. google/
  7. mrproto/
  8. project/
  9. redirect/
  10. schema/
  11. search/
  12. services/
  13. sitewide/
  14. static/
  15. static_src/
  16. templates/
  17. testing/
  18. third_party/
  19. tools/
  20. tracker/
  21. components ⇨ ../../luci/appengine/components/components
  22. gae.py ⇨ ../../../infra/luci/appengine/components/tools/gae.py
  23. gae_ts_mon ⇨ ../../../infra/appengine_module/gae_ts_mon
  24. testing_utils ⇨ ../../../infra/appengine_module/testing_utils/
  25. .babelrc
  26. .eslintrc.json
  27. .gcloudignore
  28. .gitignore
  29. .npmrc
  30. .prettierrc.json
  31. .style.yapf
  32. .vpython3
  33. app.yaml
  34. codereview.settings
  35. cron.yaml
  36. dev-services.yml
  37. import_utils.py
  38. jsconfig.json
  39. karma.conf.js
  40. main.py
  41. Makefile
  42. OWNERS
  43. package-lock.json
  44. package.json
  45. PRESUBMIT.py
  46. queue.yaml
  47. README.md
  48. registerpages.py
  49. requirements.txt
  50. settings.py
  51. test.py
  52. tsconfig.json
  53. webpack.config.js
README.md

Monorail Issue Tracker - bugs.avm99963.com

This repo is a fork of the open-source Monorail issue tracker designed to run at bugs.avm99963.com. I've made the code public so it can inspire other developers to host relatively cheap Monorail instances.

Monorail development should generally be contributed upstream, this repo will only accept changes specific to small and relatively cheap instances.

The original README.md file is here below (slightly modified where applicable):

Monorail Issue Tracker

Monorail is the Issue Tracker used by the Chromium project and other related projects. It is hosted at bugs.chromium.org.

If you wish to file a bug against Monorail itself, please do so in our self-hosting tracker. We also discuss development of Monorail at infra-dev@chromium.org.

Getting started with Monorail development

For Googlers: Monorail's codebase is open source and can be installed locally on your workstation of choice.

For local development on Linux, see Linux development instructions For local development on MacOS and Debian, see MacOs development instructions

Instructions for deploying Monorail to an existing instance or setting up a new instance are here.

See also: Common Development Problems

Testing

Python backend testing

make pytest

To run a single test:

vpython3 test.py services/test/issue_svc_test.py::IssueServiceTest::testUpdateIssues_Normal

JavaScript frontend testing

make jstest

If you want to skip the coverage for karma, run:

make karma_debug

To run only one test or a subset of tests, you can add .only to the test function you want to isolate:

// Run one test.
it.only(() => {
  ...
});

// Run a subset of tests.
describe.only(() => {
  ...
});

Just remember to remove them before you upload your CL.

Development resources

Supported browsers

Monorail supports all browsers defined in the Chrome Ops guidelines.

File a browser compatability bug here.

Frontend code practices

See: Monorail Frontend Code Practices

Monorail's design

Triage process

See: Monorail Triage Guide.

Release process

See: Monorail Deployment

User guide

For information on how to use Monorail, see the Monorail User Guide.

Setting up a new instance of Monorail

See: Creating a new Monorail instance