-
Notifications
You must be signed in to change notification settings - Fork 269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Service 'foreman' is started unconditionally #993
Comments
This was done in order to ensure it really starts. Also it can help with slow setups where you want to run the Foreman Proxy registration on the same host. I think a parameter can make sense if you want to, but the default should be |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current standard foreman configuration uses systemd socket activation to start the foreman/rails service on-demand, i.e. when a connection arrives on the 'unix:/run/foreman.sock' socket.
However, this puppet module unconditionally ensures a running systemd 'foreman.service'. This seems a redundant operation and kind of defeats the 'on-demand' part of the configuration.
The text was updated successfully, but these errors were encountered: