issues when scaling up machines on fly about epic-stack HOT 10 CLOSED

Ahh ok makes sense - glad I posted here now!

I basically lifted this logic from the stripe stack (https://github.com/dev-xo/stripe-stack/blob/fcfa7432f7c89886cbab53311d023d4d63f58544/app/routes/_layout%2B/account.tsx#L37), where it will redirect to this loader after account creation to assign the stripe customer id.

I'll modify this to handle it in a post action instead.

Appreciate it Kent! Love the work you've done with Remix & this stack 🔥

from epic-stack.

Yes that makes sense, I notice the same thing happens in the auth.$provider.callback.ts file where a connection gets created in the loader section.

from epic-stack.

We automatically redirect non-GET requests to the primary. You're doing a write on a GET request which is not recommended in general for security reasons. Is there a reason you're doing this?

I'm any case, if you need to do this, then use ensurePrimary() from litefs-js and that will fix it. But you really should avoid writing to the database on GET requests (ChatGPT can explain why).

from epic-stack.

To be clear, you said this is happening in an action, but the code you showed is in a loader. This would work fine in an action.

from epic-stack.

Sure thing! Glad to have that worked out. It would be cool if we could improve the error message there... I'll bet it's possible with Prisma client extensions.

from epic-stack.

Hi did you modify it to be in a post action @Moorst? I also have the same issue and would be interested in your implementation

from epic-stack.

I did yes, that solved it. In my case a write was attempted in a loader:

https://github.com/dev-xo/stripe-stack/blob/fcfa7432f7c89886cbab53311d023d4d63f58544/app/routes/resources%2B/stripe.create-customer.ts

so I just moved this logic to the signup action.

from epic-stack.

Good catch @argus-ralph. I've pushed an update to handle that: 4b2e70d

Thanks!

from epic-stack.

We automatically redirect non-GET requests to the primary.

Where is this happening? (so i understand ahah)

from epic-stack.

That's a feature of the LiteFS proxy server which is configured here:

Learn more about this here: https://www.epicweb.dev/tutorials/deploy-web-applications/multi-region-data-and-deployment/set-up-a-proxy-server-for-multi-region-database-support

And read up about this feature here: https://fly.io/docs/litefs/proxy/

from epic-stack.