<feed xmlns='http://www.w3.org/2005/Atom'>
<title>control-repo-template/site-modules/profile/manifests, branch 1.1.0</title>
<subtitle>puppetlabs/control-repo extended with not-so-core stuff</subtitle>
<id>https://git.pfeiffer.tech/control-repo-template/atom?h=1.1.0</id>
<link rel='self' href='https://git.pfeiffer.tech/control-repo-template/atom?h=1.1.0'/>
<link rel='alternate' type='text/html' href='https://git.pfeiffer.tech/control-repo-template/'/>
<updated>2019-02-01T00:58:13Z</updated>
<entry>
<title>Rename site directory to site-modules</title>
<updated>2019-02-01T00:58:13Z</updated>
<author>
<name>Nick Walker</name>
<email>nick.walker@puppetlabs.com</email>
</author>
<published>2019-02-01T00:58:13Z</published>
<link rel='alternate' type='text/html' href='https://git.pfeiffer.tech/control-repo-template/commit/?id=ead7f3c706657bbfae37ff40c8f919fb57c8a841'/>
<id>urn:sha1:ead7f3c706657bbfae37ff40c8f919fb57c8a841</id>
<content type='text'>
Prior to this commit, we placed modules local to a users installation
in the `site` directory.  This was just a convention and the name
`site` doesn't clearly convey what it is for.

After this commit, we place modules local to a users installation in
the `site-modules` directory.  This makes it more clear to users
that this is a directory that modules go i.  When users start
with bolt they won't even know what a control-repo is and
renaming site to site-modules gives them a better idea of why
they should put their modules with tasks in them.  Also see:

https://tickets.puppetlabs.com/browse/BOLT-1108
</content>
</entry>
</feed>
