git.lirion.de

Of git, get, and gud

aboutsummaryrefslogtreecommitdiffstats
path: root/.gitignore
Commit message (Expand)AuthorAgeFilesLines
* +gnupgH. P. 2022-03-231-0/+2
* +.vimrcH. P. 2022-03-211-0/+1
* distribution mechanism, more targets in makeH. P. 2022-03-211-0/+1
* Makefile and distribute dir for "git-less" serversH. P. 2022-03-211-0/+1
* adding distribute folder for servers which cannot reach gitH. P. 2022-03-211-0/+3
* Initial commitH. P. 2022-03-191-0/+20
d=ead7f3c706657bbfae37ff40c8f919fb57c8a841'>Rename site directory to site-modulesNick Walker 2019-01-313-0/+17 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