Browse documentation for IT-systems used by the European Environment Agency and the Eionet network.
run the container with docker-compose will make you life easy.
The production deployment is not made with
git clone and
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 'eadb' Docker image." git push origin $version git push origin master in case there's no automatic build on docker hub: docker build -t eeacms/eadb:latest otrs docker tag eeacms/eadb:latest eeacms/eadb:$version docker push eeacms/eadb:latest docker push eeacms/eadb:$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.