It's really a nice project and Thanks for focusing on Core functionality instead of UI. We need more Real-time projects like Real-time Collaboartion tool because Internet is full of MERN Blog and all repetitive stuff. 56:14 I completed backend
Thank you so much for those words and also for following along with the video. I'd love to ask you- do you have any suggestion for me in terms of my explanation or even projects you want to see on this channel?
@@AtharvaDeosthale Your explanation is very nice. I have a suggestion that on TH-cam I didn't found many videos regarding Real-time collaboration products like Google Docs or Collaborative whiteboard etc. Can you please bring some more videos on these topic because I think these projects have a great learning potential also I like that you didn't do spoon feeding by writing whole Clone code for UI and UX and you leave some work for learners so that they can also involve themselves in this project and show their creativity.
Great work btw. I have some queries. Since shadcn is an ui and you should have used it as a shared library. You are using it directly in the nextjs app, which nullifies the use of monorepo.
I would have used it in shared if I used it in different nextjs apps. Honestly, you're right this app doesn't need a monorepo, I did that because a lot of people asked for it and I think the concurrent running of apps and a Rust base would do better, but thanks for the suggestion, I'll def pay more attention on what I add into these builds
You can deploy the Next.js app on Vercel and the websocket server on a service like Render. Just remember to have the correct root directory as we are using a monorepo. So the root dir for server should be “apps/server”
You can deploy the frontend Next.js app to Vercel and the server to a service like Render. Also, do you think I should cover deployment in videos like these?
I cannot add it to this video but you can use vercel for deploying the client web app and Render to deploy the websocket server. Just make sure the root directories set on these platforms are correct, for example, for server the root should be "apps/server" because we are using a monorepo. For client, Vercel automatically detects the Next.js app, but if it doesn't, the root will be "apps/web"
It's fine. Usually sockets can be pain to deal with but Socket IO makes it a little easier. But the easiest way to explain socket is that it's an open communication channel where the client and server can send messages to each other in real time. That's how systems like chats work
Great Project sir, please i request to bring more project like these! 🙏🏻
More to come! Thanks for being here.
Man keep going just remember ui is not what we want we want core functionality stuff always
Awesome job, thank you!
It's really a nice project and Thanks for focusing on Core functionality instead of UI. We need more Real-time projects like Real-time Collaboartion tool because Internet is full of MERN Blog and all repetitive stuff.
56:14 I completed backend
Thank you so much for those words and also for following along with the video. I'd love to ask you- do you have any suggestion for me in terms of my explanation or even projects you want to see on this channel?
@@AtharvaDeosthale Your explanation is very nice. I have a suggestion that on TH-cam I didn't found many videos regarding Real-time collaboration products like Google Docs or Collaborative whiteboard etc. Can you please bring some more videos on these topic because I think these projects have a great learning potential also I like that you didn't do spoon feeding by writing whole Clone code for UI and UX and you leave some work for learners so that they can also involve themselves in this project and show their creativity.
Thanks for the suggestions! I added it to my to-do list. Expect a tutorial on that in the coming weeks.
@@AtharvaDeosthale Thank you for considering my request ❤
Great work btw. I have some queries. Since shadcn is an ui and you should have used it as a shared library. You are using it directly in the nextjs app, which nullifies the use of monorepo.
I would have used it in shared if I used it in different nextjs apps. Honestly, you're right this app doesn't need a monorepo, I did that because a lot of people asked for it and I think the concurrent running of apps and a Rust base would do better, but thanks for the suggestion, I'll def pay more attention on what I add into these builds
Amazing project!! 🔥
Thanks 🔥
Amazing content 💯
Thank you!
Amazing project, but how do I deploy this? Can we use vercel ?
You can deploy the Next.js app on Vercel and the websocket server on a service like Render. Just remember to have the correct root directory as we are using a monorepo. So the root dir for server should be “apps/server”
Great content. Any pointers on how to deploy this?
You can deploy the frontend Next.js app to Vercel and the server to a service like Render. Also, do you think I should cover deployment in videos like these?
@@AtharvaDeosthale yes that'll be great
@@AtharvaDeosthale Yes PLease add deployement part too
it would be great also.
Best Project !!! 🔥🔥
Can you put a video on deploying it
I cannot add it to this video but you can use vercel for deploying the client web app and Render to deploy the websocket server. Just make sure the root directories set on these platforms are correct, for example, for server the root should be "apps/server" because we are using a monorepo.
For client, Vercel automatically detects the Next.js app, but if it doesn't, the root will be "apps/web"
1st comment. Nice, make a video project with tanstack router.
Thanks for the suggestion. I do have a list of project ideas, I'll see which one can have tanstack router as a great fit.
13:37
bro I know jackshit about websocket
It's fine. Usually sockets can be pain to deal with but Socket IO makes it a little easier. But the easiest way to explain socket is that it's an open communication channel where the client and server can send messages to each other in real time. That's how systems like chats work