Roost - Environments as a Service
summary
Roost inspects a repo on pull request (Dockerfile, docker-compose, scripts), infers the needed stack, and automatically spins a short-lived environment that runs validations and smoke tests, exposes ephemeral preview URLs, and destroys itself on merge. The claim is concrete: turn pre-production into environments as a service so testing moves off prod and dev. Implementation is repo-driven—repo-driven inference—and the system demonstrably boots real app stacks from PRs and tears them down.
AI-written summary · about
chapters (6)
- 0:00Introduction and background
- 2:12War stories from early career
- 7:55Testing in development vs production
- 10:08Pull requests as first-class citizens
- 12:39Environments as a Service concept
- 13:41Q&A and closing remarks
related talks
25mImprove Developer Productivity with Ephemeral Environments
31mEnvironments as a Service: improve DX
50mInstant Self-contained Development Environments for Everyone
50mInstant Self-contained Development Environments for Everyone
21mEphemeral Development Environments
24mDeveloper Environments in
16mStaging Environments: A Blueprint for Pre-production
32mPreview Environments with ArgoCD