如何将MERN应用部署到Heroku？已执行部分操作后遇阻求助

Hey there! Let's start by acknowledging you've already nailed some critical setup steps for Heroku deployment—great job on those:

• Port configuration: Your app.listen(process.env.PORT || 3000, ...) is spot-on. Heroku assigns dynamic ports at runtime, so using the PORT environment variable is mandatory, and the local fallback to 3000 lets you test locally without issues.
• Mongoose connection setup: Using process.env.MONGODB_URI || 'mongodb://localhost/movies' is exactly what you need for Heroku + mLab. mLab automatically injects the MONGODB_URI environment variable when you add it as an add-on, so your app will switch between the cloud database and your local one seamlessly.
• Creating the Heroku app and mLab instance: That foundational step is done, so you're halfway there!

Since you didn't share the specific issue you ran into when pushing with git push heroku master, let's walk through the most common problems and how to fix them:

Common Deployment Issues & Fixes #

1. Git Push Fails (Build Errors) #

If your push gets stuck or throws errors during the build phase, check these:

• Ensure your package.json is in the root directory of your Git repo—Heroku uses this to install dependencies and know how to start your app.
• Verify you have a start script in package.json, like:

  "scripts": {
    "start": "node app.js"
  }
  

  Replace app.js with your actual entry file (e.g., server.js). Heroku runs this script by default to launch your app.
• Double-check that all production-required dependencies are in the dependencies section, not devDependencies. Heroku only installs dependencies in production mode.
• Look closely at the error output in your terminal—Heroku will tell you exactly what's broken (missing packages, syntax errors, etc.).

2. App Deploys But Crashes Immediately (Crash Loop) #

If the push succeeds but your app won't stay running, use Heroku's logs to diagnose:

• Run heroku logs --tail in your terminal to stream real-time logs. This will show you why the app crashed—common culprits include:
  • Database connection failures
  • Missing environment variables
  • Code errors that only show up in production
• Confirm the MONGODB_URI is set correctly: Run heroku config:get MONGODB_URI to see the value Heroku is using. If it's empty or incorrect, re-add the mLab add-on with heroku addons:create mongolab:sandbox.
• Check Mongoose version compatibility: If you're using a newer Mongoose version (v5+), useMongoClient is deprecated. Update your connection code to:

  mongoose.connect(process.env.MONGODB_URI || 'mongodb://localhost/movies', {
    useNewUrlParser: true,
    useUnifiedTopology: true
  })
  .then(() => console.log('Database connected successfully!'))
  .catch(err => console.error('Database connection error:', err));
  

• Test locally first: Run npm start on your machine to make sure the app works without errors before pushing to Heroku.

3. App Runs But Can't Connect to the Database #

If your app loads but can't access the mLab database:

• Check mLab's IP whitelist: Heroku uses dynamic IPs, so you'll need to allow all IPs temporarily for testing. Go to your mLab dashboard, select your database, then under "IP Whitelist", add 0.0.0.0/0 (note: for production, consider more restrictive settings, but this works for debugging).
• Add error handling to your Mongoose connection: As shown above, adding .catch() will log specific connection errors to your Heroku logs, making it easier to spot issues like invalid credentials or network problems.

If you can share the exact error messages from your terminal (when pushing) or Heroku logs, I can give you a more targeted solution!

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