-
Notifications
You must be signed in to change notification settings - Fork 65
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
Update the README #242
Update the README #242
Conversation
@ekohl this looks good..would you be able to add an example on how to setup ssl configuration? |
I've added some SSL examples, but haven't tested it yet. Looks like I'm still missing some of the settings on the messaging. |
This looks much more useful. I'll try it out properly tomorrow - thanks! |
Some suggestions
- There's a debug parameter, document it and explain where's the output if it's a specific file (as opposed to puppet output)
- Document emails settings (email_enabled email_from email_host email_port)
- In issue #164 we mention pulp rpm repo management, as far as I'm concerned it's mandatory for pulp standalone installation (w/o katello), it ought to be mentionned too
- default_login and default_password can be mentionned, with the default value (admin / random pwd)
- Add a quick exemple to open firewall port with crayshfix's firewalld module, since it's all about centos 7
That's it for what I'm doing. Reading the params.pp, an example with a proxy configuration might interest people too
Best regards,
|
I'm trying to simplify the usage of the admin in #248. Once that's in I'm going to expand the README. |
Updated.
I'm not sure what these exactly do so I've left them out for now.
Personally I've always used the puppetlabs-firewall module so I'm leaving this out for now. I could mention the ports used.
I noticed we have the parameter |
@ekohl guessing it was a bit of a typo when configuring this for use with Katello's installer |
Given we're going to do a major version, shall we change it to |
I'd like to get his merged on Tuesday because even if this is still incomplete, I think it's better than what we have now. Please point out any mistakes though. Suggestions for additions are also welcome and will be addressed in a separate PR. |
Still not very good, but an improvement aimed to address #143 and #241.
@rammaram06 @rgarrigue @djjudas21 if you could have a look then that'd great.