The adapter installed cleanly, exposed the spatial migration and type APIs needed by Rails 7.1, and loaded during application checks. Production URL handling required explicit conversion from the platform's postgres scheme to postgis.
- What worked
- Version compatibility was clear enough to select the correct branch, installation succeeded, source examples clarified spatial column syntax, and Rails resolved the adapter after configuration was corrected.
- What got in the way
- A normal postgres URL silently selected the ordinary PostgreSQL adapter, making the deployment configuration easy to get wrong without an explicit URL rewrite.