Heroku部署GeoDjango：PostGIS数据库无法识别且数据不显示求助

Hey there, let's break down why your GeoDjango app on Heroku isn't showing database data even though migrations completed successfully. Here are actionable steps to diagnose and fix the issue:

1. Confirm Your Heroku Database Actually Contains Data #

• Local database data doesn't automatically sync to Heroku's Postgres after migrations. Don't assume migrations populate the remote DB with your local data.
• Run this command to access your Heroku database shell:

  heroku pg:psql -a countrycompare
  

• Query your target table directly (replace compare_country with your actual model's table name):

  SELECT * FROM compare_country;
  

• If the result is empty, you'll need to import your local data. Use pg_dump to export a backup from your local DB, then run:

  heroku pg:psql < your_local_dump.sql -a countrycompare
  

2. Verify PostGIS Extension Setup for GeoDjango #

GeoDjango relies on PostGIS—this is a common oversight on Heroku:

• Connect to your Heroku DB shell (same command as above) and run these commands to enable PostGIS:

  CREATE EXTENSION IF NOT EXISTS postgis;
  CREATE EXTENSION IF NOT EXISTS postgis_topology;
  

• Double-check your settings.py database engine is set to the GeoDjango-specific backend:

  DATABASES = {
      'default': {
          'ENGINE': 'django.contrib.gis.db.backends.postgis',
          # ... other config pulled from DATABASE_URL
      }
  }
  

3. Debug Your View's Query Logic #

Sometimes migrations work, but your view's queries are failing silently:

• Temporarily enable debug mode (only for troubleshooting, disable afterward) to expose errors:

  heroku config:set DEBUG=True -a countrycompare
  

• Refresh your app and check for any visible error messages on the page.
• Alternatively, test your queries directly in the Heroku Django shell:

  heroku run python manage.py shell -a countrycompare
  

  Then run your view's query (adjust to match your models):

  from compare.models import YourModel
  print(YourModel.objects.all())
  

  If this returns an empty queryset, your issue is in the query logic or data population.

4. Validate Heroku Environment & Configs #

• Ensure your settings.py uses Heroku's auto-set DATABASE_URL (use dj-database-url to parse it):

  import dj_database_url
  DATABASES['default'] = dj_database_url.config(conn_max_age=600, ssl_require=True)
  

• Confirm ALLOWED_HOSTS includes your Heroku app domain (e.g., countrycompare.herokuapp.com):

  ALLOWED_HOSTS = ['countrycompare.herokuapp.com', 'localhost']
  

• Make sure you're using django-heroku to auto-configure GeoDjango dependencies like GDAL/GEOS:

  import django_heroku
  django_heroku.settings(locals())
  

5. Check Heroku Logs for Hidden Errors #

Silent failures often leave clues in the logs:

• Stream real-time logs while refreshing your app:

  heroku logs --tail -a countrycompare
  

  Look for database connection errors, PostGIS-related warnings, or query exceptions that aren't showing up on the frontend.

Start with verifying data exists in the Heroku DB—it's the most frequent culprit. Work through each step, and you should track down the issue quickly!

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