Replies: 2 comments 6 replies
-
Have you checked out some of the other Remix Stacks on GitHub? (https://github.com/topics/remix-stack) I'd imagine there's something that might fit your use case or you could fork something that's close to what you want and make it your own...food for thought. |
Beta Was this translation helpful? Give feedback.
-
Hi @klasco, I definitely understand the desire here, but this would distract from the primary goals and guiding principles of the project. The idea is that I select things I'm sure will work for the kinds of apps I build and people take it or leave it. Switching to postgres should only take a few minutes after bootstrapping the app thanks to Prisma. But I'm holding firm on the guiding principle of only one way to do things and limiting choices people have to make to be productive. Even if you're used to postgres, I'm confident SQLite will work just fine for you. Feel free to read the decision document about SQLite here: https://github.com/epicweb-dev/epic-stack/blob/main/docs/decisions/003-sqlite.md Thanks! |
Beta Was this translation helpful? Give feedback.
-
Hello, I am new to remix and would love to make some projects, but we mostly use Postgres and self-host our apps so if it's possible can I suggest making a sister stack in which we can choose our deployment env, server. Cause there is lot of caching going on which only works for SQLite. Like a minimal stack which everyone needs without batteries includes.
Beta Was this translation helpful? Give feedback.
All reactions