eeacms/eea-geonetwork repository overview

⁠eea.docker.eea-geonetwork

edit docker-compose-example.yml -> i.e. docker-compose.yml

run the container with docker-compose:

docker-compose up

⁠Release to production

The production deployment is not made with git clone and docker-compose build. Instead it pulls a tagged image from Docker Hub. When you have tested your changes and are satisfied, then you must push a new image up with a new version number that follows semantic versioning⁠ principles. Here is how you do it:

edit VERSION.txt
git commit VERSION.txt
version=$(cat VERSION.txt)
git tag -a $version -m "Tagging the $version release of the 'eea-geonetwork' Docker image."
git push origin $version

git push origin master

in case there's no automatic build on docker hub:
docker login
docker build --no-cache -t eeacms/eea-geonetwork:latest .
docker build --no-cache -t eeacms/eea-geonetwork:$version .
docker tag eeacms/eea-geonetwork:latest eeacms/eea-geonetwork:$version
docker push eeacms/eea-geonetwork:latest
docker push eeacms/eea-geonetwork:$version

The purpose of the procedure is to be able to redeploy the exact same image on a new host, and to be able to roll back one or more versions if the deployment has problems.