git.lirion.de

Of git, get, and gud

about summary refs log tree commit diff stats

	Commit message (Collapse)	Author	Age	Files	Lines
*	adding distribute folder for servers which cannot reach git	H. P.	2022-03-21	1	-0/+0

h=production&id=a8c6d51264bf5e9d8526283a64d29d0b1f7c16e2'>Update outdated info and links in site.pp commentsNate McCurdy 2019-05-061-14/+13 |/ | | | | | | | This commit attempts to cleanup and modernize the comments in site.pp a bit. For one thing, I've updated the docs links to point to working URL's. For another, I tried to reorganize, clarify, and deduplicate the comments. * Merge pull request #71 from npwalker/rename_site_to_site-modulesReid Vandewiele 2019-02-267-5/+5 |\ | | | | Rename site directory to site-modules | * Update README to reflect site -> site-modulesReid Vandewiele 2019-02-261-4/+4 | | | * Remove symlink site -> site-modulesReid Vandewiele 2019-02-261-1/+0 | | | | | | | | | | | | | | | | | | The symlink served for a good discussion point around change impact, but in the end having it makes for a more confusing experience overall both to new users cloning the control-repo to get started and also to anyone accustomed to "site". A new user won't miss "site". A symlink will muddy the waters over the change for long-time users. Better for clarity to be all-in and not include a symlink. | * Add symlink from site to site-modules for compatibilityNick Walker 2019-02-041-0/+1 | | | * Rename site directory to site-modulesNick Walker 2019-01-316-1/+1 |/ | | | | | | | | | | | | | | 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 * Fixed typos for 'moduelpath' and 'batteries includes' to 'modulepath' and ↵Craig Sprout 2018-12-071-2/+2 | | | | 'batteries included' * Update module examples to latest versionsNate McCurdy 2018-05-081-4/+4 | * Resolve Rubocop warningsNate McCurdy 2018-05-082-5/+5 | | | | | * Removed the useless assignment in the config_version.rb error catching * Single quote vs. double quote in Puppetfile * Merge pull request #57 from natemccurdy/config_versionNate McCurdy 2018-05-082-3/+5 |\ | | | | Config Version Improvements | * Show the short hostname, not the FQDN in config_versionNate McCurdy 2017-12-152-2/+4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is mainly a style and readability change. Prior to this, on masters whose hostname is actually their FQDN, the config_version script would show the entire FQDN. On nodes with really longs FQDN's, it was not very nice to look at. This takes the hostname of the master, splits it on dots (.) and takes the first segment. Now this: compile-master-02.int.lab.dmz.company-name.net-production-48fd18ab Is this: compile-master-02-production-48fd18ab | * Use the puppet-agent ruby in config_version.rbNate McCurdy 2017-12-151-1/+1 | | | | | | | | | | | | | | | | Prior to this, the config_version.rb script (used for r10k) attempted to use the system ruby to parse the script. This caused problems on Puppet masters that don't have `ruby` in PATH. This fixes that by hardcoding the puppet-agent's ruby in the shebang. * | Merge pull request #61 from natemccurdy/readme_markdownNate McCurdy 2018-03-131-93/+94 |\ \ | | | | | | Improve the README | * | Simplify the info about the RampUp ProgramNate McCurdy 2018-03-131-5/+4 | | | | * | Add a tree view with descriptions of important filesNate McCurdy 2018-02-061-0/+23 | | | | * | Reorganize the README and improve the documentation