Thanks Ken, good to see some basic React Query stuff, and the auto-generated types from the rails schema was interesting too. Would love to see create, update, delete functionality the React Query way with useMutation.
We ran separate repos in production and never had any real issues without versioning. I would probably setup the pipeline to deploy API first then the frontend after. Could also use feature flags. I think you can even have these issues when using next.js only - vercel tried to solve but not sure how well it works as I’ve never used that feature.
To be honest, not sure. It’s been a convention to use the src directory for many years in js so probably just a preference thing. You can throw all your other directories into src as well, but either way probably works!
This is exactly what my team needed - one guy works on this and hasn't done it before. Just forwarded it.
Nice!
Awesome...
Suddenly appear in my home RUclips, keep up Sir
Thanks and welcome :)
Wow thank you! Was just looking for this kind of setup for my app! Wanna move my React & Rails project from a monolith to a monorepo like this one.
Love that it was useful. I’ve just released a follow up which shows how to add the crud endpoints as well :)
Thanks Ken, good to see some basic React Query stuff, and the auto-generated types from the rails schema was interesting too. Would love to see create, update, delete functionality the React Query way with useMutation.
Thanks mate! Had another request for the same so I think I’ll have to add it to the list
Thanks Ken. Videos are very helpful to follow along
Thanks mate! Hope you got something useful out of it :)
Wow i have been waiting for this thank you ken always
Hope you enjoyed it!
Let me know what you want to see next!
@@kengreeff rails graphql api, clean architecture and more production stuff logging monitoring... 🙏
🎉
Love it 🔥🔥🔥🔥🔥
Thanks mate!
Excellent!
Glad it helped!
Question: how do you deploy these 2 repositories together? Any kind of versioning needed?
We ran separate repos in production and never had any real issues without versioning. I would probably setup the pipeline to deploy API first then the frontend after. Could also use feature flags. I think you can even have these issues when using next.js only - vercel tried to solve but not sure how well it works as I’ve never used that feature.
whats the difference between using app directory directly vs src/app directory?
To be honest, not sure. It’s been a convention to use the src directory for many years in js so probably just a preference thing. You can throw all your other directories into src as well, but either way probably works!
Btw, please make another tutorial using Phoenix Framework with Next JS
Unfortunately I have zero experience with Phoenix so can’t provide much value there. I do have a follow up to this video though :)
Can u make a simple crud with ror and nextjs for us? Button create, edit, delete and show more
Hey Pablo, thanks for the great suggestion. I'll see what I can do if you make sure you subscribe and hit the bell icon ;)
Done ;)