Draft project plan

Rob

• Doing a load test w/ the current setup, including measuring response times

• Figuring out key database configuration:
  • Which DB provider should we use (Fly, Heroku, Supabase, other?)
  • Master/slave setup
  • Maybe distributed reads with central writes
  • Postgres backups / recovery plan

Keith

• Bug monitoring (Sentry)
• Uptime monitoring
• Implement the Claude front-end theme and add a theme abstraction

Still need to decide who for:

• Changing ActiveStorage config from Postgres to Cloudflare's S3 alternative. Regardless of what we learn from our load test, we need to get these big files out of the database)
• Stripe billing to charge recurring fee & end-of-month true-up (everyone uses the same Stripe subscription portal these days)
• Password reset feature (including sending emails, I used to use Sendgrid but who is best these days?
• Ability to track accrued token cost real-time (I'm helping on this Issue)

Things we might not need to do but keeping here so I don't forget

• Implement SolidCache / Russian doll caching for the views that read from the DB
• Improve queue architecture (depends on what we learn from load test)
• Verifying Fly rolling (?) deploy (they have a few different configuration options)
• Potentially some Fly Dockerfile configuration changes if we discover we need to make them
• Potentially some Cloudflare config changes since it may not be interacting quite right with Fly