I just made my docker-compose setup for gibbon available. Since I am still evaluating Gibbon I am not sure how long I will be able to maintain it, but nonetheless, maybe it is a starting point for better projects.
I tried to script the setup and update process to use an environment variable with the version number. It should work, but I have not been through a Gibbon upgrade yet.
To easily revert errors I added automatic backups to the database container. A dump is created via a crontab - container every hour.
This should be useful for beginners like me to ensure a safe, easy to repair, playground.
Thanks for taking the time to share this. I’ll most likely not have time to try it right now, but will try and come back to it. In the meantime, I’ll post to our developer Slack group, as you might get some interest there.
I just submitted a PR a few moments ago for a small bug in the simple docker-compose YML which I believe is an issue on specific versions of docker-compose iirc. I am working on adding some health checks to your custom containers in an attempt to have a CI check put in place on there.
I am only discovering this Github repo a year later. This is amazing. Well done Paul. What is the chance that the Gibbon project will create an image on the Docker Hub. If permitted, I would be interested in being a part of this project (with the little knowledge that I have). I have successfully installed using @PaulLebmann’s Github repo; I have it running behind the Traefik reverse proxy. I have even experienced the upgrade process.
Hi achief, Docker definitely seems like a good way to get Gibbon up and running fast. Our core team has its hands full with existing aspects of Gibbon, and so don’t have any plans to create an image on Docker Hub. However, we are happy to facilitate community volunteers who wish to do this. Cheers, Ross.