https://github.com/suizer98/geodirectus
My dockerised Directus CMS application to enable easy and customisable integration with geospatial data
https://github.com/suizer98/geodirectus
bash cms directus docker postgresql
Last synced: 3 months ago
JSON representation
My dockerised Directus CMS application to enable easy and customisable integration with geospatial data
- Host: GitHub
- URL: https://github.com/suizer98/geodirectus
- Owner: Suizer98
- Created: 2024-09-09T06:01:01.000Z (almost 2 years ago)
- Default Branch: main
- Last Pushed: 2025-06-03T08:22:40.000Z (about 1 year ago)
- Last Synced: 2025-06-03T19:31:35.297Z (about 1 year ago)
- Topics: bash, cms, directus, docker, postgresql
- Language: Shell
- Homepage:
- Size: 10.3 MB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: readme.md
Awesome Lists containing this project
README
# GeoDirectus
This is a project exploring self-hosting a Directus CMS using Docker and PostGIS for geospatial data.

## Deploy
Run the project locally:
1. Clone the repo:
```bash
git clone https://github.com/suizer98/geodirectus.git
```
2. cd to it and spin it up:
```bash
cd geodirectus
docker-compose up
OR
podman-compose up
```
Access the CMS at:
http://localhost:8055/admin
## Local development
You can straightaway build the self hosting Directus using the sample postgres data in this repo. However if you need to start from scratch better to remove the sample data:
```bash
sudo rm -rf postgres/data
docker-compose down -v
docker-compose up
OR
podman-compose down -v
podman-compose up
```
## Backing up and restoring self hosting databases
Since it is running in Docker instances, we can do below:
```bash
docker exec -t geodirectus-postgres-1 pg_dump -U postgres postgres > postgres/backup.sql
```
To restore using the `backup.sql`, we can edit `postgres/backup.sql` to avoid restoration errors:
```sql
CREATE SCHEMA IF NOT EXISTS tiger;
CREATE SCHEMA IF NOT EXISTS tiger_data;
CREATE SCHEMA IF NOT EXISTS topology;
```
Make sure we add `IF NOT EXISTS` for these 3 lines from PostGIS image. Also the backup.sql is looking for the same user name, so you probably need to watch out with the POSTGRES_USER variable.
To sneak peek to your postgres relevant settings and data, go to the volume mounted:
```bash
# Not recommended, this is just testing to override permission
sudo chmod -R 777 postgres/data
ls postgres/data
```
## Features
- Geospatial data handling via PostGIS
- Dockerised setup, allowing fully customised configuration