On 3/31/19 9:54 PM, Fabian Arrotin wrote: > So the idea is that each tool (or complete toolchain) that we need to > use to build/produce whatever should be available on a long-term. > So the 'hey, I found a container that does this today' isn't usually a > good idea, except if we can come with a receipe (Dockerfile) that we can > use to rebuild the needed containers/layers every week , or have some > RPM pkgs already available too. > > If we look at the current solution used for www.centos.org, it's built > in nanoc, for which we have a container available through > https://registry.centos.org > From a user PoV, it's explained in the README.md file how to get it and > so build locally the website for local rendering, etc > > From a sysadmin PoV, here is the Dockerfile that is used to rebuild > every week the container/and get automatic scan from the > registry.centos.org pipeline (kudos to the team in charge of this btw !) > Container : https://registry.centos.org/arrfab/nanoc > Dockerfile/CCCP for registry.centos.org : > https://github.com/arrfab/container_nanoc probably I've completley misunderstood your email ... but imho I can't see a problem to provide the same mechanism (docker) as it exists for nanoc. Maybe another solution could be, to create an ansible role for providing the page and a docker container for developing. cheers, florian