Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upMove most Salt docs in tree #549
Conversation
|
I think I'm generally OK with this. @edunham what do you think? |
|
|
|
As long as we replace the corresponding wiki docs with pointers to the docs in tree, I'm fine with this. My only concern is that if we end up with parallel sets of docs on the same topic, one or the other will fall out of date and deciding which to follow becomes an unnecessary burden. |
5831d39
to
1c758fc
This also includes Vagrant information, and should cover all the steps of a normal Salt workflow. This does not (yet) include information about setting up new Salt masters/minions, or how to restart various services cleanly after a deploy. Moving docs in-tree ensures they stay up to date with code changes, as opposed to having to remember to update the wiki after long review cycles. The corresponding sections will be removed from the wiki and replaced with pointers to the in-tree docs.
|
Yes, I'll replace those sections on the wiki with references to the in-tree docs after this merges. Thanks for looking over this! @bors-servo r=edunham |
|
|
Move most Salt docs in tree This also includes Vagrant information, and should cover all the steps of a normal Salt workflow. This does not (yet) include information about setting up new Salt masters/minions, or how to restart various services cleanly after a deploy. r? @edunham @larsbergstrom cc @Ms2ger per [this comment](#545 (comment)) <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/saltfs/549) <!-- Reviewable:end -->
|
|
|
I updated the Buildbot and SaltStack Administration pages on the wiki to remove the duplicate information and add pointers to the in-tree docs. |
aneeshusa commentedDec 8, 2016
•
edited by larsbergstrom
This also includes Vagrant information,
and should cover all the steps of a normal Salt workflow.
This does not (yet) include information about
setting up new Salt masters/minions,
or how to restart various services cleanly after a deploy.
r? @edunham @larsbergstrom
cc @Ms2ger per this comment
This change is