Creating a new Monorail instance

  1. Create new GAE apps for production and staging.
  2. Configure GCP billing.
  3. Fork and configure every part of it, especially trusted domains and “all” email settings.
    1. Change num_logical_shards to the number of read replicas you want.
    2. You might want to also update */* files.
  4. Create new primary DB and an appropriate number of read replicas for prod and staging.
    1. Set up IP address and configure admin password and allowed IP addr. Instructions.
    2. Set up backups on primary DB. The first backup must be created before you can configure replicas.
  5. Set up log saving to bigquery or something.
  6. Set up monitoring and alerts.
  7. Set up attachment storage in GCS.
  8. Set up spam data and train models.
  9. Fork and customize some of HTML in templates/framework/header.ezt, footer.ezt, and some CSS to give the instance a visually different appearance.
  10. Get From-address allowlisted so that the “View issue” link in Gmail/Inbox works.
  11. Set up a custom domain with SSL and get that configured into GAE. Make sure to have some kind of reminder system set up so that you know before cert expire.
  12. Configure the API. Details? Allowed clients are now configured through luci-config, so that is a whole other thing to set up. (Or, maybe decide not to offer any API access.)
  13. Gain permission to sync GGG user groups. Set up borgcron job to sync user groups. Configure that job to hit the API for your instance. (Or, maybe decide not to sync any user groups.)
  14. Monorail does not not access any internal APIs, so no allowlisting is required.
  15. For projects on, coordinate with that team to set flags to do per-issue redirects from old project to new site. As each project is imported, set it's moved-to field.