tum-gis / 3dcitydb-docker-postgis Goto Github PK

Replace deprecated Dockerfile MAINTAINER cmd with the new LABEL cmd.

What labels should be used?

Add scripts to /usr/local/bin for easier database creation, deletion and reset.
Example call inside container:

# Create a new 3DCityDB
create3DCityDB.sh <DBNAME> <SRID> <SRSNAME>
create3DCityDB.sh "munich-db" 31468 "EPSG:31468"

# delete an existing 3DCityDB
delete3DCityDB.sh <DBNAME>

# reset (=remove all data from DB)
reset3DCityDB.sh <DBNAME>

• Remove unused PostGIS template db

Use the official PostGIS Docker image as base for the 3DCityDB image instead of adding PostGIS manually to the official PostgreSQL images.

https://github.com/postgis/postgis

This should be possible by simply issuing a new commit, e.g. after data has been importer to a 3DCityDB instance running on a docker container.
This would be a powerful option to provide data, as one could hand out a fully setup 3DCityDB with the requried data already stored in it.

Builds are failing after the latest Alpine/Postgre updates. Updated Dockerfile reference here:

https://gitlab.com/equalos/skaffold/blob/master/postgis/docker/postgis/Dockerfile

Please let me know if you find any issues.

Build fails because due to changes to proj alpine package:
See here:

• https://gitlab.alpinelinux.org/alpine/aports/issues/10612
• timescale/timescaledb-docker#75
• postgis/docker-postgis#146

Test/create builds for custom 3DCityDB version. Currently, only v3.3.1 and v3.0.0 have been tested.

Test behavior, if invalid SRID is provided with docker run. E.g. if the provided SRID is unknown to the 3DCityDB.

The new version of postgres base image requires new values. Change documentation.

See:

Error: Database is uninitialized and superuser password is not specified. You must specify POSTGRES_PASSWORD to a non-empty value for the superuser. For example, "-e POSTGRES_PASSWORD=password" on "docker run".

You may also use "POSTGRES_HOST_AUTH_METHOD=trust" to allow all
connections without a password. This is not recommended.

See PostgreSQL documentation about "trust":
https://www.postgresql.org/docs/current/auth-trust.html

Extend existing documentation.