Deploy pgMaps
Manage maps and GIS data in PostgreSQL databases
pg-maps
Just deployed
Deploy and Host pgMaps on Railway
Open-source tool for managing maps and geospatial data in PostGIS-enabled PostgreSQL databases
About Hosting pgMaps
It is required that your set three environment variables: POSTGRES_URL: Your PostgreSQL connection string. By default, the app will create up to four tables in the public schema (_pgmaps_basemaps, _pgmaps_connections, _pgmaps_folders, _pgmaps_maps) to store its own data.
APP_PASSWORD: Password protecting the app. Without it, anyone with the URL could obtain read/write access to your PostgreSQL database.
DSN_ENCRYPTION_KEY: 32-byte hex key used to encrypt saved connection strings at rest. Generate with openssl rand -hex 32.
Common Use Cases
- Easily load spatial files into your PostgreSQL database
- Visualize and edit geospatial data at scale
- Create, manage, and share live maps
Dependencies for pgMaps Hosting
- PostgreSQL connection string
- Docker
Deployment Dependencies
None
Why Deploy pgMaps on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying pgMaps on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
pg-maps
nogurtmon1/pg-maps:latestAPP_PASSWORD
Password protecting the app. Without it, anyone with the URL could obtain read/write access to your PostgreSQL database.
POSTGRES_URL
Your PostgreSQL connection string. By default, the app will create up to four tables in the public schema (_pgmaps_basemaps, _pgmaps_connections, _pgmaps_folders, _pgmaps_maps) to store its own data.
DSN_ENCRYPTION_KEY
32-byte hex key used to encrypt saved connection strings. Generate with openssl rand -hex 32.
