As it stands, I have everything wired to production even when I'm developing. However, folks should be able run the project without access to production.
There's a lot to untangle here but I should do it so that I can use this repository as an example of how I do things to show others. If the repo doesn't run happily locally, that's kinda bunk.
Things that would have to happen:
[ ] Include a docker-compose that will run a Postgres instance
[ ] Seed script for Prisma to full up that Postgres database
[ ] Make sure Prisma connects to that local Postgres when real credentials are not present
[ ] Fill up avatars and game images with placeholders if Firebase variables are not present
[ ] Give fake data (or empty data) in place of Twitch API when Twitch tokens are not present
What am I missing?
This is a fairly substantial amount of work that perhaps should only happen once the existing codebase is done being cleaned up. I have problems with it even myself and I wouldn't expect anyone else to be able to make meaningful changes to it. Unless someone shows up really enthusiastic to work on kittr, I won't prioritize this over customer-facing needs.
As it stands, I have everything wired to production even when I'm developing. However, folks should be able run the project without access to production.
There's a lot to untangle here but I should do it so that I can use this repository as an example of how I do things to show others. If the repo doesn't run happily locally, that's kinda bunk.
Things that would have to happen:
What am I missing?
This is a fairly substantial amount of work that perhaps should only happen once the existing codebase is done being cleaned up. I have problems with it even myself and I wouldn't expect anyone else to be able to make meaningful changes to it. Unless someone shows up really enthusiastic to work on kittr, I won't prioritize this over customer-facing needs.