-
Notifications
You must be signed in to change notification settings - Fork 12
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
Make the localconfig.template.yml explain what rather than how #57
Comments
I'll need to write up that reference doc first (or if you or anyone else wants to try writing a draft as a way to learn how everything works...), but once that's done, I agree with making this change. |
Another change I want to make: instead of
That way if you were deploying something fancy that already has its own playbook, like swag_dev, but wanted to add the webmail system to it, you would just run put something like this...
and provision.py would create and run a playbook like this:
Mentioning this partly as a note to myself, partly in case someone has comments, and partly so you don't want to kill me if you do write a draft and then I change things unexpectedly. :P |
Where should the reference documentation be? I can maybe put things there as I encounter problems and find ways to fix them (if I find ways to fix the problems I encounter, that is). Can't say that it will be comprehensive from the start though, but good to get it started... |
I'd say put it in the wiki (new doc, not the setup doc), and just include "DRAFT" in the title so people know not to treat it as authoritative yet. |
I think that the localconfig.template.yml file has... well... a bit too much documentation...
Maybe we can cut it down for example the PROFILE section to something like this, also describing the options of what the user is likely to want to do:
The text was updated successfully, but these errors were encountered: