git.lirion.de

Of git, get, and gud

summaryrefslogtreecommitdiffstats
path: root/README.md
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #102 from ekohl/update-linksReid Vandewiele 2022-03-031-5/+5
|\ | | | | Update links in README
| * Update links in READMEEwoud Kohl van Wijngaarden 2021-10-121-5/+5
| | | | | | | | | | | | All links to Puppet's Code Manager were broken. The Puppet 5 links are updated to version 7. The Gitlab links redirect somewhere else. The direct link saves users a redirect.
* | Merge pull request #105 from taikaa/readme-updatesReid Vandewiele 2022-03-031-1/+1
|\ \ | | | | | | (docs) corrected Gitlab initial password information
| * | (docs) corrected Gitlab initial password informationTA 2021-11-171-1/+1
| |/
* / Jumpstart programme is not live (#107)David Sandilands 2022-03-031-3/+1
|/ | | | | | | | | * Jumpstart programme is not live We should remove the mention of the jumpstart programme which appears orphaned and unmaintained * Update README.md Co-authored-by: Reid Vandewiele <reid@puppet.com>
* Update README.mdBen Ford 2021-05-051-1/+1
| | | Co-authored-by: Reid Vandewiele <reid@puppet.com>
* Add template instructionsBen Ford 2021-05-051-1/+8
|
* Update README.md Vu Long Tran 2020-10-211-2/+1
| | | | | Sounds good Co-authored-by: Reid Vandewiele <reid@puppet.com>
* Update README.mdVu Long Tran 2020-10-191-1/+1
| | | Updating Code Manager link to the latest - https://puppet.com/docs/pe/2019.8/code_mgr.html. As old link has been updated.
* Update README to reflect site -> site-modulesReid Vandewiele 2019-02-261-4/+4
|
* Fixed typos for 'moduelpath' and 'batteries includes' to 'modulepath' and ↵Craig Sprout 2018-12-071-2/+2
| | | | 'batteries included'
* 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 documentationNate McCurdy 2018-02-061-23/+27
| | | | | | | | | | | | This commit moves the "where did all the previous code go" section to the bottom as it's been a while since that change was made. Nowadays, people new to Control Repositories will find this and won't understand the reference as they never knew about previous versions. Now the README starts right away with information on what this project is and how to use it. Also cleaned up some of the Markdown syntax to make it easier to read.
* Fix markdown list syntaxNate McCurdy 2018-02-061-75/+50
|
* Add Bitbucket/Stash instructionsPeter Souter 2018-02-011-4/+28
|
* Update README.mdJody Des Roches 2017-11-151-1/+1
| | | Small typo fix
* Add GitHub instructionsAlex Harden 2016-11-081-3/+23
| | | Per Issue https://github.com/puppetlabs/control-repo/issues/26
* Update README with new Ramp Up Program URLNick Walker 2016-05-271-1/+1
|
* light editing, mostly for stylejbondpdx 2016-05-111-37/+26
|
* Reduce the scope of the control-repo to mostly an exampleNick Walker 2016-03-291-177/+44
| | | | | | | | | | | | | | | | | | | Prior to this commit, the control-repo was an example of the structure of a control repo but it also included puppet code to help setup code manager and instructions to get that all setup in a very specific way. This was great for users that wanted to follow those instructions exactly but wasn't great for people just looking for an example to start from. After this commit, the control-repo will be just an example once again and a new repo somehwere else will pop up to provide the explicit instructions on how to use the example with code manager. There are links added to puppetlabs/control-repo to a new repo that will have a version of the code that once lived in puppetlabs/control-repo
* Corrected documentation grammar.Jerald Sheets 2016-02-241-1/+1
|
* Update README with info on how to upgrade from 2015.2Nick Walker 2016-01-041-50/+52
| | | | | | | Mostly reorganized the README to be 2015.3 first and then have some extra info at the bottom about upgrading from 2015.2. Added a blurb about what the control-repo provides.
* Add an exec to create the Deploy Environments RBAC RoleNick Walker 2015-12-281-8/+2
| | | | | | | | | Prior to this commit there was a requirement for the user of this repo to create a RBAC role in order for code manager to work. After this commit an exec statement will curl the RBAC API to create the role one time and hopefully it works otherwise the exec will not run again.
* Add instructions for testing code managerNick Walker 2015-12-181-1/+34
| | | | | | | Also, add a table of contents to the README. I generated the table of contents using https://github.com/ekalinin/github-markdown-toc.go
* Final steps to make Code Manager workNick Walker 2015-12-181-31/+42
| | | | | | | | | | - Moved ssh key generation and git deploy key out of the puppetmaster profile and into zack_r10k and code_manager - Swapped code manager into the all_in_one role - Made a 2015.2 all_in_one role if users prefer to use it - Conditionally move all existing code out of environmentpath to allow file sync to sync files - Update the README to compliment the new puppet code
* Cleanup README to generalize urls and add notes about testingNick Walker 2015-11-241-5/+4
| | | | | | | Remove a specific reference to the npwalker namespace in a git clone command. Add some notes that this has only been tested against 2015.2.z.
* Merge branch 'production' of https://github.com/npwalker/control-repo into ↵Nick Walker 2015-11-241-0/+177
|\ | | | | | | merge_npwalker_control_repo
| * Multiple fixes to the READMENick Walker 2015-10-221-12/+12
| | | | | | | | | | | | fix step 16 and 17 being out of order fix a step that referred erronously to step 4 change the numbering to be reflective of actual numbering
| * Clean up the README so it works from top to bottomNick Walker 2015-10-211-42/+20
| | | | | | | | | | I removed some extraneos notes I had and added a few more bits of documentation.
| * Remove notes about making control-repo publicNick Walker 2015-10-201-4/+0
| |
| * Change the zack/r10k webhook to not authenticateNick Walker 2015-10-201-1/+31
| |
| * Change to using the webhook without mcollectiveNick Walker 2015-10-161-2/+4
| | | | | | | | | | | | In order to complete the change I refactered the webhook into its own set of profiles, one with mcollective and the other without.
| * update READMENick Walker 2015-09-291-3/+5
| |
| * Update README to remove --mirror from git cloneNick Walker 2015-09-251-1/+1
| |
| * Update README some moreNick Walker 2015-09-241-62/+110
| |
| * Update README partiallyNick Walker 2015-09-221-15/+34
| | | | | | | | | | | | | | I made some updates to the README that I never committed. I'm probably going to change some of this but it's more useful with these additions than without.
| * Update READMENick Walker 2015-08-181-8/+22
| |
| * Update the README with more specific instructionsNick Walker 2015-08-181-0/+26
| | | | | | | | This is still a WIP
| * Update the README, add an all_in_one_pe roleNick Walker 2015-08-131-9/+55
| | | | | | | | | | | | | | | | | | | | | | Updating README for instructions on how to use the control-repo by putting it in your own git server and then using the r10k answers during installation of PE. Removing the manifest for configuring r10k using zack/r10k. Added a role that can be used to bootstrap an all-in-one PE installation.
| * Update README.mdNick Walker 2015-05-261-0/+6
| |
| * Update README.mdNick Walker 2015-05-151-1/+1
| |
| * Update README.mdNick Walker 2015-01-141-1/+3
| |
| * Update README.mdNick Walker 2015-01-141-1/+2
| |
| * Add the READMENick Walker 2015-01-131-0/+6
|
* Initial commitorodabaugh 2015-08-111-0/+2