Growing internal tooling from the console up
summary
Projects move from one-off console fixes to repeatable ops: live demos use Rails console for investigation, turn recurring fixes into rake tasks, pipe alerts into Slack and then into an app with ActiveAdmin or a custom admin dashboard. Stack specifics show Rails 5.1, Ruby 2.5, React front end, MySQL, Redis, Sidekiq, Kubernetes on Google Cloud. Claims include cutting point-dev daily triage from 15–45 minutes to about five and uncoupling prod access from routine troubleshooting.
AI-written summary · about
chapters (32)
- 0:00Intro
- 0:32Q: How old is your codebase?
- 1:41About me
- 3:13The Stargate application
- 4:27About Brent from The Phoenix Project
- 5:23What we are going to cover
- 6:06Goals
- 8:38About the problem space
- 9:51Operational Needs
- 10:25Context-switching is painful
- 10:50Sample issues
- 11:57Approach the issues iteratively
- 12:49Improving issue visibility
- 13:11Improving resilience
- 14:14Involve your team
- 14:38Example of team involvement
- 16:08What's the console good for?
- 16:30Why SQL from the Rails console?
- 16:49How we use the console
- 17:49Rails console benefits
- 18:13Rails console caveats
- 19:03Safe use of the production console
- 20:18Automate what you can, make it visible
- 20:49Notification Benefits
- 21:45Notification Caveats
- 22:47Automation
- 24:15Rails Admin Interfaces
- 26:04Why build your own?
- 33:09That's a lot of tools
- 33:36Central Questions, revisited
- 35:24Additional questions
- 37:11Resources
