Migrating Slope Ninja to ZEIT for Fun & Profit
summary
Shows a full migration: Slope Ninja moves from Heroku to ZEIT, cutting bills and avoiding Heroku’s root‑domain and dyno scheduling limits. Deployment uses now CLI with immutable builds, site hosts front end, API, workers and cron jobs; cron jobs run in a single process now with a plan to spin parallel workers via the now API. Uses ZEIT’s free DNS, migrates other projects too, and reports the whole process as practically effortless.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:12From recruiter to engineer
- 3:00What is Slope Ninja
- 5:35Production deployment challenges
- 6:41AWS and Heroku issues
- 8:52Discovering ZEIT Now
- 10:45ZEIT Now benefits
- 11:27Closing remarks
related talks
35mKubernetes the easy way
31mSo Long, Hoboken: Migrating a Huge Production Codebase from Sinatra to Rails
35mMultitenancy - Build Vs. “Buy”: Zcaler’s Journey
01h 01mFrontend Deployments Made Frictionless: Hands-On with Catalyst Slate
11mTransforming Front-End Deployment: Fast, Fluid, Frictionless
26mNo gain without pain a story of scaling CI with Zuul
35mSite Reliability Engineering...
44mMigrating a Monolith to Kubernetes