– Rebuilding a similar app with a new tech stack is easier the 2nd time around

– Motivation for using Rails and live coding features right next to his client

– What the app does at a high level and what some of the screens do

– The app is running Rails 4.2 and it’s humming along with minimal maintenance

– Stripe handles accepting donations and keeping things as simple as possible

– Processing over $30 million dollars since the site went live

– It’s worth checking out which payment providers are available in different countries

– Using an older version of Stripe’s API but it’s super stable

– A couple of gems from 2015 which helped build this app

– (1) standard Heroku Dyno for the web app and (1) 2x size Dyno for the worker

– Postgres, Redis and Resque are being used along with Heroku’s cron scheduler

– Sending bulk emails out can be scary

– Using Rbenv locally to manage things in development

– The reasons for picking Heroku were mainly to avoid any type of ops work

– What it’s like to develop a new feature and push it up to production

– Not doing traditional TDD but tests are still written

– Heroku is in charge of performing daily database backups

– Handling background worker spikes with popular donation pages

– Tagging the current user in Rollbar errors and then emailing customers ASAP

– Best tips? Keeping it simple really drives down your maintenance

– CJ’s has a YouTube channel and a personal site at https://cjav.dev