-
Notifications
You must be signed in to change notification settings - Fork 10
/
pillar.example
38 lines (38 loc) · 1.57 KB
/
pillar.example
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
gitolite:
shell: /bin/bash
home: /home
repository_url: https://github.com/sitaramc/gitolite.git
revision: v3.6.1
ssh_admin_pubkey_name: gitolite-admin
ssh_admin_pubkey_source: salt://ssh_keys/admin.pub
ssh_pubkey: ssh-rsa here_goes_your_public_ssh_key== admin@example.com # default admin key if user's ssh_pubkey is not defined
ssh_pubkey_source: salt://ssh_keys # default SSH pubkey source
# In some setups SSH is not available on localhost
admin_host: localhost
#admin_host: my.host.test
users:
- username: git
# from the docs:
# default umask gives you perms of '0700'; see the rc file docs for
# how/why you might change this
# If you change this, you'll need to manually adjust the permissions of already present files.
# This MUST be set as a string in order to preserve the leading zeros.
umask: '0077'
# Add these users to the $username group (in this example: git)
group_add: []
# group_add:
# - www-data
ssh_admin_pubkey_name: gitolite-admin
ssh_admin_pubkey_source: salt://ssh_keys/admin.pub
ssh_pubkey: ssh-rsa here_goes_your_public_ssh_key== git@example.com
shell: /bin/zsh
managed: True # Manage via Salt; Include gitolite.managed!
gitolite_conf_source: salt://gitolite/files/my_gitolite.conf.jinja
ssh_pubkey_source: salt://ssh_keys # May be ommitted
ssh_pubkeys:
- alice
- bob
- name: mallory
remove: True
# Set GIT_CONFIG_KEYS to enable 'config key=value' in the repo config file
git_config_keys: '.*'