能否将Node/Express+React全栈应用部署至GoDaddy子域名？

Hey Tim, great question! Deploying your Node/React full-stack SPA to a subdomain on your friend's GoDaddy-hosted site is totally doable—here's a step-by-step guide tailored to your scenario:

1. 先确认GoDaddy主机的Node.js支持 #

Since your friend previously deployed PHP-based Kirby sites, first verify their GoDaddy hosting plan supports Node.js:

• Shared/cPanel Hosting: GoDaddy’s cPanel includes a Node.js Manager tool (check under the "Software" section). If it’s missing, they may need to upgrade their plan or enable Node support via GoDaddy support.
• VPS/Dedicated Hosting: These plans natively support Node.js, so you’ll just need to ensure you can run Node processes in the background.

2. 配置子域名指向主机目录 #

First, set up the subdomain to point to a dedicated folder on their hosting:

• Log into your friend’s GoDaddy account, navigate to their domain’s management dashboard.
• Add a new subdomain (myReactNodeApp) and map it to a folder in their hosting root (e.g., public_html/myreactnodeapp—this will be where your React static files live, or your full-stack app if bundled together).

3. 部署你的全栈应用 #

There are two common approaches, depending on how you structured your app:

Option A: Separate React frontend + Express backend (recommended) #

This keeps your frontend static and your backend isolated, which is more stable for shared hosting:

1. Build & deploy the React frontend:
   • In your React project, run npm run build to generate optimized static files in the build folder.
   • Upload all files from the build folder to the subdomain’s mapped directory (e.g., public_html/myreactnodeapp).
2. Deploy the Express backend:
   • Upload your Express project to a non-public folder on the host (e.g., private_html/myreactnodebackend—this prevents direct public access).
   • Use GoDaddy’s Node.js Manager to configure the backend:
     • Point to your entry file (e.g., server.js).
     • Assign a port (GoDaddy shared hosting typically restricts ports to a specific range—check their docs for allowed values).
   • Add a reverse proxy rule to your subdomain’s .htaccess file to route API requests to the backend:

     RewriteEngine On
     # Route all /api requests to the Express backend
     RewriteRule ^api/(.*)$ http://localhost:YOUR_BACKEND_PORT/$1 [P,L]
     

   • Start the Node backend via the Node.js Manager (or use pm2 start server.js if the host allows it, to keep the process running in the background).

Option B: Bundled React + Express (single deployment) #

If your Express app serves the React static files directly:

1. Bundle your app:
   • In your Express project, configure it to serve React’s build files:

     const path = require('path');
     app.use(express.static(path.join(__dirname, 'client/build')));
     
     // Catch all routes and return React's index.html (for SPA routing)
     app.get('*', (req, res) => {
       res.sendFile(path.join(__dirname, 'client/build', 'index.html'));
     });
     

   • Run npm run build in your React project, then move the build folder into your Express project (e.g., client/build).
2. Deploy the bundled app:
   • Upload the entire Express project to the subdomain’s mapped directory.
   • Use GoDaddy’s Node.js Manager to configure the app (point to server.js, assign a port).
   • Add a reverse proxy rule to .htaccess to route all subdomain traffic to the Node app:

     RewriteEngine On
     RewriteRule ^(.*)$ http://localhost:YOUR_APP_PORT/$1 [P,L]
     

   • Start the app via the Node.js Manager or pm2.

4. Test & Troubleshoot #

• Visit myReactNodeApp.HisGoDaddyDomain.com to check if the React app loads, and test any API endpoints to ensure they connect to the backend.
• If you see 404 errors: Verify the .htaccess rules are correct, and that your React router is configured for the subdomain (if using client-side routing).
• If you see 500 errors: Check that the Node app is running, the host’s Node version matches your development environment (add an engines field to package.json to specify), and that the port you’re using is allowed.

内容的提问来源于stack exchange，提问作者Tim Tolley