I’ll take care of the PR. Since this is my first PR for Foreman, do I need
to raise an issue and reference it? Or will referencing #18732 suffice?
We’re using a docker-compose file for the time being while we get ready to
move over to Kubernetes, hopefully by next year. We’re governmental
organization running a bit over 400+ nodes, using Puppet + Foreman as the
ENC. Right now, I’m trying to refactor my repository so that’s in line with
yours. You can view the work at https://github.com/luksi1/docker-foreman.
The issue in which I’m running the refactor is branch “issue-26”.
Hopefully, this branch will get merged shortly and we will be able to start
contributing to the project with more and more meaningful feedback!
As a side note, where do you want the documentation for this? I haven’t
seen any Docker or docker-compose information in the docs, but maybe I’m
missing something. In case there isn’t any, do you want the documentation
in the manual? In a markdown file on the site in GitHub? I do personally
think docker-compose is a nice way to on-board people with minimal set-up
so they can try Foreman out and see Foreman’s value quickly before deciding
whether or not to move forward. I would be more than happy to do this, I
just need to know if I’m sending a PR to the project or if I need to send
over the documentation in another form. Let me know what you think.