The reason I’ve opted to trial Render.com is because it appears to be the only ‘official’ serverful option for Redwood deployments. (Is it still the case that Redwood realtime must be on a serverful deployment?).
Am I missing something here?
I should add, to be clear: I’ve implemented this as per the docs here, and all is working well locally.
Redwood v6.6.4 (will upgrade to v7 once I have a functioning deployment).
Node version = 20 (moved up from 18 to get around OOM errors during Render build phase)
Yarn = 4.0.2
This might seem counter intuitive but v7 releases support for graphql subscriptions and the server file. So you will need to upgrade to get graphql subscription support
Happy to upgrade now if we think that helps, but the realtime features are working fine locally on v6 (experimental). It’s only an issue after deploying to Render. Would v7 make a difference here?
Just wanted to clarify that Render isn’t the only official serverful option for Redwood deployments. Coherence and Flightcontrol are both serverful, as well as Baremetal though that’s more advanced.
Just another heads up that I was able to reproduce the deploy to Render with subscriptions not working and think I have a fix in the works. Will keep you updated and have an RC out for you to try, but that would be a v7 RC. Could also provide you with a workaround though probably. But if you haven’t upgraded to v7 and it’s not too much of a lift that would be helpful in the meantime.
Hey @voltore, no worries—sorry for the belated response here. I did get a patch that hopefully alleviates the memory issue in Render (see Release v7.0.3 · redwoodjs/redwood · GitHub) but it doesn’t seem like their platform (or at least their free tier) supports SSE which is necessary for realtime. We asked for clarification but are still waiting on an official response from their team.
In the meantime Coherence is working so I’d encourage you to try them out if you’re keen on using realtime. The setup command for Coherence is going to be patched today in a similar manner but the deploy here in Redwood’s deploy target CI is working as a reference: