[ Request ] Let's improve Remix SaaS together!

dev-xo / remix-saas

A Lightweight, Production-Ready Remix Stack for your next SaaS Application.

https://remix-saas.fly.dev

MIT License

1.17k stars 82 forks source link

[ Request ] Let's improve Remix SaaS together! #232

Open dev-xo opened 5 months ago

dev-xo commented 5 months ago

Hello folks! 👋

Although Remix SaaS is currently in good shape, there are some small improvements we could make in order to provide a better template for us all.

Due to the lack of time I currently have, I'll leave here a few possible improvements, in case we could all start a talk and slowly look into them.

Possible Improvements

[ ] TypeScript Server File #240
[ ] Improved Testing Setup (Currently very basic) #239
[ ] More Payment Providers like Paddle or Lemon Squeezy
[ ] ... something else maybe?

Any doubts, ideas, or suggestions, feel free to reach out to me on X/Twitter or simply continue the talk here on GitHub!

HananoshikaYomaru commented 4 months ago

Thanks for doing this. I am following your Remix Saas template on one of my side project.

I am interested in testing setup with Playwright.

I struggle a bit on how to test the login. it will be nice if you provide some example.

dev-xo commented 4 months ago

TypeScript Server File: #240 Requires a fix, as I'm not able to successfully deploy. Any insights on it will be welcome!

D-Pagey commented 3 months ago

Hey - this looks like a great stack. However, doesn't SQLite on Fly.io need to have LiteFS to sync the volumes across multiple machines? Having 1 machine isn't prod-ready according to Fly.io as far as I know.

dev-xo commented 3 months ago

Hello @D-Pagey.

LiteFS has been left out of the main Stack idea in order to keep it as simple as possible for others to set up the initial template, as dealing with initial complexity could cause some relatively new users to struggle more than they should.

Do you have any idea of the complexity of implementing LiteFS, and if that could slow down the initialization of the template?

Thanks.

D-Pagey commented 3 months ago

Hey @dev-xo,

Yeh that makes sense. The reason I'm aware of this is because I'm trying to implement LiteFS myself and struggling with it, so was hoping this stack had it already worked out 😂

In my limited understanding, running multiple machines is essential for any production environment, and so LiteFS would be a must have for anyone taking this stack to prod.

I don't think its too hard so will power through and can come back and answer that question, I must just be missing something simple 🤞

dev-xo commented 3 months ago

I'm a bit busy lately @D-Pagey, so if you can come up with a little PR or some insights about it, we could look into implementing it for the stack!

Updated the TODO List :)

D-Pagey commented 3 months ago

I'm a bit busy lately @D-Pagey, so if you can come up with a little PR or some insights about it, we could look into implementing it for the stack!

Updated the TODO List :)

@dev-xo yeh if I work it out I'll come back and update 😁

ryan-richards commented 3 months ago

I'm a bit busy lately @D-Pagey, so if you can come up with a little PR or some insights about it, we could look into implementing it for the stack!

Updated the TODO List :)

@dev-xo yeh if I work it out I'll come back and update 😁

Just sharing this here, looks like Kent is using LiteFS and has a similar setup with fly. https://github.com/kentcdodds/epic-ai