GH-120 Documentation updates

  Minor formatting changes, specifically capitalization of r10k at the start of sentences.
  README.mkd:
    Update documentation links to reflect the changes below.
  docs/common-patterns.mkd:
    New document showing common patterns to advise users.
  docs/dynamic-environments.mkd:
    Add link to workflow-guide.mkd.
  doc/dynamic-environments/configuration.mkd:
    Move invalid_branches description to this file.
  doc/dynamic-environments/git-environments.mkd:
    Comment on ability to use subversion.
    Clarify the details of 'how it works'.
  doc/dynamic-environments/introduction.mkd:
    Update introduction to reflect environmentpath beginning with puppet v3.5.
  doc/dynamic-environments/quickstart.mkd:
    Provide alternate method to access a dynamic environment.
  doc/dynamic-environments/usage.mkd:
    Clarify how forge modules are treated.
  doc/dynamic-environments/workflow-guide.mkd:
    Completed workflow guide.
Either, really. I know that "sub modules are not supported" based on irc
discussions but not the specifics. How would you explain that more clearly?

On Tuesday, October 28, 2014, Adrien Thebo <notifications@github.com> wrote:

> In doc/common-patterns.mkd:
>
> > +This guide provides common patterns seen in the r10k community. These patterns
> > +are, of course, simply a guide. Understand why you are or are not using a
> > +specific pattern before implementing it.
> > +
> > +Repository Setup
> > +----------------
> > +
> > +Use a [Control Repo](http://www.jeffmalnick.com/blog/2014/05/16/r10k-control-repos/)
> > +to store your **Puppetfile**.
> > +
> > +Hiera data should be in the Control repo OR as a separate source in
> > +**r10k.yaml**. Any **hiera.yaml** in the Control repo will be ignored on a per
> > +environment basis, locating it at **/etc/puppet/hiera.yaml** is prefered.
> > +
> > +Each puppet module should be contained in its own forge module or repository.
> > +Multiple modules in a single git repository with sub-modules are not supported
>
> I still don't know what this means, precisely - is this using Git
> submodules or containing modules in a subdirectory of a Git repository?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/adrienthebo/r10k/pull/210/files#r19503812>.
>


-- 


Rob Nelson
rnelson0@gmail.com