Congratulations on the progress on the topic! (I saw this mentioned in a related thread.)
The Docker Compose file in the foreman repo references both the container image from Quay as well as the build context.
image: quay.io/foreman/foreman:develop
command: bundle exec bin/rails server -b 0.0.0.0
build:
context: .
So, this setup is clearly meant for developing The Foreman, correct?
Should we split up the Compose configuration into separate files, e.g. by moving the development pieces into a docker-compose.override.yml file (as suggested by the Docker documentation)?
This way we could make the picture clearer, separate the concerns of the application architecture + dependencies and development. This could help to keep a suggested reference implementation for a base setup in a single file. We could then add a Kubernetes configuration mirroring that setup (that we would have to keep aligned).
What do you think?
Full disclosure and background information: My motivation here is to have a single file or small set of configuration files that are “production ready” (labeled “The Foreman certified”
) that one could curl or wget w/o having to clone the entire repository, for setup automation freed of any manual tasks.