-
Notifications
You must be signed in to change notification settings - Fork 237
Draft project plan
Keith Schacht edited this page Jul 24, 2024
·
10 revisions
- 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
- Voice mode
- Implement the Claude front-end theme and add a theme abstraction
- Bug monitoring (Sentry)
- Uptime monitoring
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) - https://github.com/AllYourBot/hostedgpt/pull/465- 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)
- 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