gnuviech/gvasalt
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
gvasalt/pillar/gnuviechadmin/init.sls

19 lines
489 B
Text
Raw Normal View History

add PostgreSQL database and message queues to vagrant box
2015-10-04 20:18:44 +02:00
gnuviechadmin:
make settings configurable via pillar, default to local
2015-10-11 14:11:11 +02:00
deploymenttype: local
add PostgreSQL database and message queues to vagrant box
2015-10-04 20:18:44 +02:00
mailfrom: admin@gnuviech-server.de
adminemail: admin@gnuviech-server.de
sitename: Gnuviech Customer Self Service
domainname: localhost
devinstance: True
minosuid: 10000
minosgid: 10000
osuserprefix: usr
osuserhomedirbase: /home
osuserdefaultshell: /usr/bin/rssh
Improve salt setup This commit improves the salt setup of the Vagrant box: - Salt output is reduced to log level warning - Hosts entries are created for the internal IPs of all planned gva component VMs - .bashrc and a .bash_functions sourced from it are now managed for the vagrant user - the VM name has been changed to gva.local - recent salt versions do not depend on m2crypto anymore, therefore it is now installed before x509certificate functions are called - the rabbitmq_vhost for gva is now setup before any users are created because the previous implementation was broken with recent salt versions - the gnuviechadmin-locale-data-compile step has been simplified because Django 1.9's compilemessages takes care of recursive .mo file compilation - pillar data has been separated by role (especially queue permissions and credentials) - salt configuration is now unified with gvaldap
2016-01-29 18:34:40 +01:00
uploadserver: gvafile.local
Synchronize salt configuration with gvaldap
2016-01-31 16:34:53 +01:00
ldap_domain: gva.local
ldap_url: ldap://gvaldap.local
ldap_base_dn: dc=gva,dc=local
ldap_groups_ou: groups
ldap_users_ou: users
Reference in a new issue Copy permalink