docker-postgis | Dockerfile for postgis | Continuous Deployment library

by kartoza Shell Version: Current License: GPL-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | docker-postgis Summary

docker-postgis is a Shell library typically used in Devops, Continuous Deployment, Docker applications. docker-postgis has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

Dockerfile for postgis

Support

Quality

Security

License

Reuse

Support

docker-postgis has a low active ecosystem.

It has 565 star(s) with 302 fork(s). There are 39 watchers for this library.

It had no major release in the last 6 months.

There are 9 open issues and 186 have been closed. On average issues are closed in 167 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of docker-postgis is current.

Quality

docker-postgis has 0 bugs and 0 code smells.

Security

docker-postgis has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

docker-postgis code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

docker-postgis is licensed under the GPL-2.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

docker-postgis releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

It has 379 lines of code, 28 functions and 12 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of docker-postgis

Get all kandi verified functions for this library.

docker-postgis Key Features

No Key Features are available at this moment for docker-postgis.

docker-postgis Examples and Code Snippets

No Code Snippets are available at this moment for docker-postgis.

Community Discussions

Trending Discussions on docker-postgis

ERROR: unsatisfiable constraints when installing PostGIS on the Alpine Docker image

QUESTION

ERROR: unsatisfiable constraints when installing PostGIS on the Alpine Docker image

Asked 2020-Jan-23 at 19:59

Ok, so the task seems pretty easy! Use an Alpine image (as it is light-weight and secure) to perform some PostgreSQL DB creation/migrations. I'm using the following Dockerfile using the code here:

...

ANSWER

Answered 2020-Jan-23 at 19:59

The code on github contains another image postgres:11-alpine comparing to image defined in question: alpine:latest.

Packages gdal-dev, geos-dev, protobuf-c-dev are no longer in edge repo testing branch, they were migrated to stable v3.11 repository. Also proj4-dev was renamed to proj-dev, which is also in stable v3.11 repository.

So to fix the Dockerfile we just need to install above packages from v3.11 repo, ie change this part of code:

Source https://stackoverflow.com/questions/59882544

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install docker-postgis

There are three modalities in which you can work with SSL:. By default, the image is delivered with an unsigned SSL certificate. This helps to have an encrypted connection to clients and avoid eavesdropping but does not help to mitigate man in the middle (MITM) attacks. You need to provide your own, signed private key to avoid this kind of attacks (and make sure clients connect with verify-ca or verify-full sslmode). Although SSL is enabled by default, connection to PostgreSQL with other clients i.e (PSQL or QGIS) still doesn't enforce SSL encryption. To force SSL connection between clients you need to use the environment variable.
Optional: using the shipped snakeoil certificates
Forced SSL: forced using the shipped snakeoil certificates
Forced SSL with Certificate Exchange: using SSL certificates signed by a certificate authority
The image supports replication out of the box. By default, replication is turned off. The two main replication methods allowed are.
Streaming replication
Logical replication

Support

If you require more substantial assistance from kartoza (because our work and interaction on docker-postgis is pro bono), please consider taking out a Support Level Agreement.

Find more information at: