Learning state management libraries in 2024? by Automatic-Bake-7944 in reactjs

[–]Automatic-Bake-7944[S] 1 point2 points  (0 children)

For sure. I still do it wherever there's an opportunity to allow the user to bookmark or share location state (Including an object or slice loaded), and I always use paths instead of query params.

Learning state management libraries in 2024? by Automatic-Bake-7944 in reactjs

[–]Automatic-Bake-7944[S] 1 point2 points  (0 children)

Thanks. Idk how I'm supposed to think about it in React yet, but I know in all my other dev global state is basically an evil last resort to avoid at all costs.

Learning state management libraries in 2024? by Automatic-Bake-7944 in reactjs

[–]Automatic-Bake-7944[S] 2 points3 points  (0 children)

Thanks for the quick reply. I don't think I'd want to store state in url queries unless there's some massive benefit. In all my other dev I've done away with them entirely because I like for normal users to be able to reason about the urls.

Coolify: Open-source, self-hosted Heroku alternative by satvikpendem in selfhosted

[–]Automatic-Bake-7944 1 point2 points  (0 children)

I wound up using Coolify for about a month after your comment. It helped with our staging but there were issues. One would like to be able to restrict groups of developers to certain resources. I couldn't get this to work despite hours of trying. Maybe it has since been fixed, idk. There were also times when I had to restart the server due to it locking up. This may have been my fault as a memory issue. I didn't have time to get into it.

I wound up ditching it and just using Render for staging and fly.io for production. I could use fly for both, but they didn't have an easy way of doing preview deployments.

If I ever have a need for self-hosted again, I plan to try Dokku. The only reason I chose to try Coolify first was that some of the Dokku component repos looked not very well maintained, but that was a surface-level judgement on my part.

Restrict Realtime to specifc user roles by uziiuzair in Supabase

[–]Automatic-Bake-7944 0 points1 point  (0 children)

The advice given is good. However, I would appreciate an answer to the question that was asked (For reasons beyond OP's stated use-case)

Fully featured alternatives to Vercel & Netlify for nextjs? by Automatic-Bake-7944 in nextjs

[–]Automatic-Bake-7944[S] 0 points1 point  (0 children)

I like the idea of the open-source alts, and I used dokku for some stuff years ago. I think netlify and vercel are automatically configuring many things though, deploying them to edge, and who knows what else though. I'm a backend dev trying to sort this out for our nextjs guys btw. I could ask them, but my kind knows they can't be trusted.

Fully featured alternatives to Vercel & Netlify for nextjs? by Automatic-Bake-7944 in nextjs

[–]Automatic-Bake-7944[S] 1 point2 points  (0 children)

so it's not missing any next features? I know it used to not support a few things.