Forge Home

gitolite

Installer for gitolite on Centos and RHEL

25,832 downloads

7,641 latest version

5.0 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 1.2.12 (latest)
  • 1.2.11
  • 1.2.10
  • 1.2.9
  • 1.2.8
  • 1.2.7
  • 1.2.6
  • 1.2.5
  • 1.2.3
  • 1.2.2
  • 1.2.1
  • 1.1.9
  • 1.1.8
  • 1.1.7
  • 1.1.6
  • 1.1.5
  • 1.1.4
  • 1.1.3
  • 1.1.2
  • 1.1.1
  • 1.1.0
  • 1.0.3
  • 1.0.2
  • 1.0.1
  • 1.0.0
  • 0.2.0
  • 0.1.5
  • 0.1.4
  • 0.1.3
  • 0.1.2
  • 0.1.1
  • 0.1.0
released Jun 7th 2017
This version is compatible with:
  • Puppet Enterprise 2023.5.x, 2023.4.x, 2023.3.x, 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x, 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >=4.0.0
  • , ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'jlcox-gitolite', '1.2.12'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add jlcox-gitolite
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install jlcox-gitolite --version 1.2.12

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download
Tags: git

Documentation

jlcox/gitolite — version 1.2.12 Jun 7th 2017

gitolite

Installs a gitolite git repository service, with optional hooks to r10k for managing puppet environments.

Parameters

git_key

Administrators public ssh key for setting up the system. Defaoult value is undef.

admin_user

Name for the admin user that the key will be associated with. Default value is admin.

git_key_type

The type of key for the administrator (defaults to ssh-rsa)

git_home

root directory for the repository. Defaults to the git users home direcotry (/home/git)

auto_tag_serial

Adds an auto incremental serial tag to each commit. Defaults to false.

r10k_update

Run r10k after git commit to deploy both environments and modules This determins what needs to be done and runs either deploy module or deploy environment. It will run both if a Puppetfile is changed. Defaults to false.

r10k_location

Location of the r10k executable that the hook will call. Used to populate the sudoers file correctly. If the module puppet/r10k is installed it will use the value for the $r10k_path fact, otherwise defaults to /bin/r10k.

Examples

Simple Gitolite Managed Repositories

In order to manage repositories that have no connection to puppet, all you need to provide is an ssh key value. Note that this uses the ssh_key resource type underneath, so it should only be the key and not the key type prefix, nor the comment.

class { gitolite:
  git_key => 'some key val',
}

Integrating r10k

If this is installed on your puppet master machine, then the repository can be integrated with r10k. Hooks will be added to repositories so that any pushes to these repositories result in r10k pulling the updates immediately.

class { gitolite:
  git_key     => 'some key val',
  r10k_update => true,
}

Authors

Jason Cox j_cox@bigpond.com

Copyright

Copyright 2014 - 2017 Jason Cox, unless otherwise noted.