Feature #2375
closed
Foreman installer should not depend on anything outside repository
Description
For my client, I synchronize the foreman repository with mrepo for installations.
The puppet/foreman machine does not have any authorization on the proxy, therefore the foreman-installer is unusable.
As the documentation is not complete yet when foreman-installer is not used (I should participate more), I'm unable to quickly install a new foreman instance.
One solution could be to document the missing parts like ENC script
Another solution is to create RPMs from missing puppet modules and distribute this through the yum repo.
Updated by Dominic Cleal about 11 years ago
- Status changed from New to Feedback
Sorry, I'm not sure I understand the issue description.
The installer uses packages from the Foreman repositories, plus EPEL if you're on RHEL, plus your base OS repos.
ENC scripts etc are all provided as part of the installer modules themselves. The installer provides all of the Puppet modules required for configuration, there aren't any other modules required.
Could you please explain the issue again? thanks.
Updated by Benjamin Papillon about 11 years ago
My bad, I read the README.md before checking the code.
The module does not depend on any external sources except, as you said, baseos, EPEL and foreman repos.
You were quick to answer =)
Regards
Benjamin
Updated by Dominic Cleal about 11 years ago
- Status changed from Feedback to Closed
Ah thanks, I see now. I think I've improved the README a bit here:
https://github.com/theforeman/foreman-installer/pull/42
I've removed all reference to downloading individual modules as that's just getting too complex and instead referred users to the stable packages (as our manual describes), or to just use git --recursive.