install.sh
, it collects information about your system and passes that to the ansible-playbook
command. The script is idempotent, meaning you can run it many times and get the same result.system_hostname
, mysql_root_password
, or php_memory_limit
.install.sh
runs, it creates a simple Ansible inventory file in the same folder that install.sh
resides. This file contains a single entry using just the hostname by default.install.sh
script will tell ansible-playbook to use that file.inventory
file is the key to customizing the configuration of your server.install.sh
script uses a separate inventory
file than the default Ansible inventory (at /etc/ansible/hosts
). This is to remain unobtrusive to the system. In the future, we will likely start using the default inventory system.inventory
in the same directory as install.sh
. You can place custom variables in there in the form of an "Ansible Inventory".server_hostname
:server_hostname=devshop.mydomain.com
is the variable that Ansible will use to try and set the system hostname of this machine.ansible-galaxy
command and DevShop's requirements.yml
file: https://github.com/opendevshop/devshop/blob/1.x/requirements.ymlansible-galaxy install
:defaults/main.yml
file. In this file are all the available variable names you can use, along with their default values.templates
folder. Most configuration files on the system come from these templates.php_memory_limit
is in the defaults/main.yml
file located at https://github.com/geerlingguy/ansible-role-php/blob/master/defaults/main.yml#L48 and is written to the templates/php.ini.j2
file at https://github.com/geerlingguy/ansible-role-php/blob/master/templates/php.ini.j2#L36inventory
file, then run install.sh
again to reconfigure your system. The Ansible playbooks are smart enough to restart services if a configuration file changes.