Get information about Origami components, services, and repositories
origami-registry-ui
Bronze
Decommissioned
https://registry.origami.ft.com
Heroku
No
No
No
No
ActiveActive
FullyAutomated
FullyAutomated
NotApplicable
PartiallyAutomated
PartiallyAutomated
Manual
This is a Node.js application, and mostly exists as a presentation layer over the top of the APIs for Origami Repo Data and Origami Codedocs.
Most of the logic for the service is in the routes, and the most complex parts of the app relate to transforming data from the APIs into something that's useable by the view layer.
You can find more information on the live site.
This application is not critical outside of office hours, please contact the Origami team and we'll fix when we're in the office.
If no member of the Origami team is available within office hours, check the status of healthchecks for more information or try restarting all of the dynos across the production Heroku apps (pipeline here).
If the application is failing entirely, you'll need to check a couple of things:
- Did a deployment just happen? If so, consider rolling it back.
- Check the Heroku metrics page for EU apps, to see what CPU and memory usage is like (pipeline here)
- Check the CDN (Fastly) is caching pages as expected.
Always roll back a deploy if one happened just before the thing stopped working – this gives you the chance to debug in the relative calm of QA.
TODO
No failover is in place for this because it is a bronze service.
No data is stored by this system.
The application is deployed to QA whenever a new commit is pushed to the master branch of this repo on GitHub. To release to production, a git tag is created and push to GitHub.
The only key used by this application is for Origami Repo Data. We rotate this manually.