Changes between Version 20 and Version 21 of DevWikiDockerTesting

Timestamp:

01/30/23 10:49:15 (21 months ago)

Author:

robe

Comment:

--

DevWikiDockerTesting

@@ -10 +10 @@
 Here is an example of how you can pull an image, retag and push to postgis-docker.osgeo.org
 
-
+**FOR DEVELOPMENT**
 {{{
 #To develop and test using this image, do the following
+cd ~/
 mkdir projects
 
@@ -23 +24 @@
   --mount type=bind,source="$(pwd)/projects",target=/projects \
   docker.osgeo.org/postgis/build-test:trisquel3  tail -f /dev/null
+
 
 cd projects
@@ -63 +65 @@
 Docker Hub is used for Github-actions testing and there is also a postgis for production use. The main link to all is [https://hub.docker.com/u/postgis]
 
-* [https://hub.docker.com/r/postgis/postgis] - has production images managed by a community of PostGIS users. To become a contributor go to [https://github.com/postgis/docker-postgis]
+* **FOR PRODUCTION** [https://hub.docker.com/r/postgis/postgis] - has production images managed by a community of PostGIS users. To become a contributor go to [https://github.com/postgis/docker-postgis]
 
-* [https://hub.docker.com/r/postgis/postgis-build-env] - has development images managed by a PostGIS Development team set aside for regression testing.  Do not use these for production use as they don't even have postgis installed on them. You can find the docker files here [https://github.com/postgis/postgis-build-env]
+* **FOR DEVELOPMENT** [https://hub.docker.com/r/postgis/postgis-build-env] - has development images managed by a PostGIS Development team set aside for regression testing.  Do not use these for production use as they don't even have postgis installed on them. You can find the docker files here [https://github.com/postgis/postgis-build-env]
 
+The postgis-build-env images don't have PostGIS installed on them at all, but have all the key dependencies needed to compile PostGIS.  The version **latest** in development versions proj, gdal, geos, postgresql, and sfcgal.  It is used to catch possible issues with other upstream projects.
+
+You can set it up much the same as the docker.osgeo.org development suite detailed earlier.
+
+
+**FOR DEVELOPMENT**
+{{{
+#To develop and test using this image, do the following
+cd ~/
+mkdir projects
+
+#this container has no built in entry point to keep it running, 
+# create a fake one as discussed here - https://levelup.gitconnected.com/keep-docker-container-running-for-debugging-fc2dfa39472c
+
+docker pull postgis/postgis-build-env:latest
+#this might take a minute or so after download to start up
+docker run -d \
+  --name postgis-build-env \
+  --mount type=bind,source="$(pwd)/projects",target=/projects \
+  postgis/postgis-build-env:latest  tail -f /dev/null
+
+cd projects
+git clone https://git.osgeo.org/gitea/postgis/postgis.git
+
+
+
+#once started you can attach to it
+docker exec -it postgis-build-env /bin/bash
+
+# in the postgis-buildenv container, you should be able to do
+# below copied from https://git.osgeo.org/gitea/postgis/postgis/src/branch/master/ci/github/run_coverage.sh
+cd /projects/postgis
+# Flags for coverage build
+CFLAGS_COV="-g -O0 --coverage"
+LDFLAGS_COV="--coverage"
+
+#TODO fix this, container starts up using postgres, and so these fail if mounting an external source folder
+/usr/local/pgsql/bin/pg_ctl -c -l /tmp/logfile -o '-F' start
+./autogen.sh
+./configure CFLAGS="${CFLAGS_COV}" LDFLAGS="${LDFLAGS_COV}" --enable-debug
+make -j 4
+make check
+make install
+
+#any changes you make to your local folder projects/postgis, will show in the container /projects/postgis
+
+#in the container
+
+# To stop it do
+docker stop postgis-dev
+
+# if you need to remove the container to get a new version do
+
+docker rm postgis-dev
+
+}}}