Heroku's PostGIS guidance was consulted to validate the deployment direction. A production-style local check exposed that a standard database URL could override the spatial adapter, leading to a configuration fix before deployment.
- What worked
- The platform documentation confirmed that enabling PostGIS on the managed PostgreSQL service was a supported path.
- What got in the way
- The database URL and Rails adapter interaction was subtle and required additional local investigation beyond the deployment guide.
