Absolute legend, clean explanation. Step-by-step and with no skips/edits/movie magic (you're excused for the npm start edit because I get why you wouldn't want a revert step inside a tutorial :P) My only criticism is in the VERY important app.get('*', ...) function and possibly app.use(static usage with express.static) as someone (like myself) may have stumbled on this video without watching previous bits ... those were only mentioned rather than explained. Overall excellent tutorial and helped me a lot!!
Thank you again ! Been watching this video and the one about deploying the app on EC2, both greatly educative. One question though, the way on both occasions that you pass the React built files to the client is through the back end, and I'm a bit lost, isnt it usually directly the role of the HTTP server (apache or enginx) ? Is this commom practice to call an express app that responds with the built react client app, and I'm just poorly educated on the subject ? (perfectly reasonnable possibility ^^)
Regarding your question, it is indeed common practice to serve static files through an HTTP server like Apache or Nginx. However, using a Node.js server to serve the static files is also a valid approach and has its advantages, especially when you want to build a more complex web application. One advantage of using a Node.js server is that it allows you to have more control over the server-side logic and provides more flexibility when it comes to serving dynamic content. Additionally, using a Node.js server allows you to easily integrate with other backend services that you may have. That being said, using an HTTP server to serve static files is still a valid approach, and it might be a better fit for some use cases. It ultimately depends on your specific needs and the requirements of your project. I hope that helps clarify things.
Absolute legend, clean explanation. Step-by-step and with no skips/edits/movie magic (you're excused for the npm start edit because I get why you wouldn't want a revert step inside a tutorial :P)
My only criticism is in the VERY important app.get('*', ...) function and possibly app.use(static usage with express.static) as someone (like myself) may have stumbled on this video without watching previous bits ... those were only mentioned rather than explained.
Overall excellent tutorial and helped me a lot!!
Yo What if, im using VITE?
Thank you again ! Been watching this video and the one about deploying the app on EC2, both greatly educative.
One question though, the way on both occasions that you pass the React built files to the client is through the back end, and I'm a bit lost, isnt it usually directly the role of the HTTP server (apache or enginx) ?
Is this commom practice to call an express app that responds with the built react client app, and I'm just poorly educated on the subject ? (perfectly reasonnable possibility ^^)
Thank you for watching my videos and I'm glad you're finding them informative.
Regarding your question, it is indeed common practice to serve static files through an HTTP server like Apache or Nginx. However, using a Node.js server to serve the static files is also a valid approach and has its advantages, especially when you want to build a more complex web application.
One advantage of using a Node.js server is that it allows you to have more control over the server-side logic and provides more flexibility when it comes to serving dynamic content. Additionally, using a Node.js server allows you to easily integrate with other backend services that you may have.
That being said, using an HTTP server to serve static files is still a valid approach, and it might be a better fit for some use cases. It ultimately depends on your specific needs and the requirements of your project.
I hope that helps clarify things.
what if i use Vite?
i same problem with you, i use vite too, how do you deploy your project vite ?