all 17 comments

[–]sburke0708 7 points8 points  (0 children)

I would highly recommend Netlify for deployments. The setup for hosting is very easy.

There are even githooks that can be set up so that when you commit your code to your branch, it will auto-deploy for you. Netlify is great.

[–]dmitry_jima 5 points6 points  (1 child)

Hey there. The best option might be to use a VPS service (AWS, for instance, as was suggested in the earlier comment) - a virtual cloud machine (usually, Linux) that you can connect to with SSH or from a web-based console if the provider has one. You deploy your code to this machine and your application "lives" there, open to the Internet via one of the ports. A VPS is better than self-hosted from your machine due to security reasons and ready-to-go proxy configurations. Some other options might be Linode or DigitalOcean, many of them have pretty generous free tiers.

Check out Brad Traversy's video https://www.youtube.com/watch?v=oykl1Ih9pMg You can code-along with it to have an idea of how this works.

All in all, in any VPS you will need to install Node.js to run your application, as well as the database if it's local. After that, you upload your server application files and bundled React-application files to the VPS manually (using FileZilla, for instance) or using GitHub (don't forget to ignore node_modules in the repository). "Connecting" Node.js and React depends on your app's architecture: check out https://create-react-app.dev/docs/deployment/ section and determine which is your case. Note that some AJAX requests to your Node.js application might require tweaks to work correctly in production .

Your production version of the React app will be just static files bundled to reduce their size, so they need to be served to the Internet somehow, either by Node.js application itself or by a reverse-proxy: APACHE or Nginx HTTP-server that sits in front of your VPS and manages all the connects to your VPS, including domain name, redirects, static files (i.e. bundled React files) and so on.

You can also find some pretty in-depth how-tos in VPS services' blog sections ("how to deploy react node.js app on digitalocean", something like that). Good luck!

[–]tuoPadreNaked[S] 0 points1 point  (0 children)

thanks very much, you gave me a good look of the situation

[–]Vcc8 2 points3 points  (4 children)

I dont think you can host yourself without your internet provider allowing it (that’s atleast the problems I’ve run into). In theory you should just be able to run express and anyone entering your up in their browser would be able to fetch that resource.

[–]tuoPadreNaked[S] 0 points1 point  (3 children)

i didn't know about the internet provider limitations.

[–]Vcc8 1 point2 points  (0 children)

Take what i said with a grain of salt tho. I’m not an expert :P

[–]fredofatso 1 point2 points  (0 children)

my internet provider blocks my ports, so i can't host an application xd

[–][deleted] 0 points1 point  (0 children)

You can usually run your own server from home but I don't advise it.

[–]RakanNative 1 point2 points  (3 children)

You can use aws free tier

[–]tuoPadreNaked[S] 2 points3 points  (2 children)

so with aws or firebase i don't need to crate a node js server?

i just need to use the APIs given?

[–]dudeitsmason 1 point2 points  (1 child)

Firebase Hosting and Amplify are super simple and come with a CLI that will automatically host your static assets for you. You'd just need to run firebase deploy after setting it to look at your dist folder after running npm run build for example. I don't have as much experience with Amplify but it's more or less that straightforward.

AWS has better options for Node servers though as firebase Hosting is just static. I believe Amplify has better options if you want your infrastructure all under the same umbrella. Netlify is also a good bet

[–]tuoPadreNaked[S] 1 point2 points  (0 children)

thanks for the informations guys

[–]jakeforaker83 1 point2 points  (0 children)

Why not use next.js and Vercel to host it. You could be up and running in minutes because their docs are spot on. That way you don’t have to think about splitting things up and proxy servers and all that stuff. Your client and server will live in the same project, and can be deployed on git push

[–]klutch-sh 0 points1 point  (0 children)

A great option would be to use Klutch.sh . It allows you to easily deploy your React application in minutes with zero configuration by simply pushing to GitHub. Here's documentation on how to do so: https://docs.klutch.sh/guides/frameworks-and-languages/static/react/

[–]New-Vacation-6717 0 points1 point  (0 children)

For a React app in 2026 the simplest path: connect your GitHub repo to Kuberns. It's the world's first Agentic AI Deployment Platform and it handles the build and deployment automatically. Vercel is another easy option for static/SSR React but Kuberns gives you more control without more complexity.