city-of-bloomington / ansible-role-apache Goto Github PK

As we install the same packages on different hosts, the modules that are enabled in apache are different. This makes it confusing to write playbooks to deploy web applications.

We should pick a set of base modules that this role installs. Anything else should be left up to a playbook to deploy.

We are starting to need to use the status module to debug stalls and timeouts. Ansible should deploy these configuration changes to all apache instances.

• VHost for localhost
• apt-get install lynx

Apache gets installed with a long list of DirectoryIndex files. For our work, we really only want it to have index.html. We need figure out a way to have the apache role check for the long list and leave only index.html.

The trick will be that we want the PHP role to be able to add index.php. So the apache role should probably somehow know about the PHP role. I'm not really sure how best to do this.

Ansible now has an openssl module. We should try to use that to generate the self-signed certificates, instead of the command module.

For all the web servers hosting applications behind our proxy, we would like to have the actual client IP addresses in the logs. This way, when we analyze the log files, we'll know where the traffic is really coming from.

We could probably create an ansible variable to specify trusted proxies. We would use the presence of that variable to activate the module and add extra stuff to 000-default.conf

Sometimes when we're running a web application playbook, we just want to update the site configuration files, without touching all the other stuff (ssl keys, modules, etc.)

We should add tags so playbooks can call for just the site configuration tasks to run.

Each of our web servers has different custom configuration that needs to be applied. We want to version the apache configuration for all our hosts, and ansible's inventory seems like the best place to do that.

We'll probably need to put the configuration into the host's public vars as data variables. Similar to what we do for the SSL certs.

There are often times where a particular host needs a special configuration directive set.

The old way of doing apt with-items is deprecated. The new way is to declare a variable for all the package names.

New style for apt-get install

- name: "Install Dependencies"
  apt:
    name: "{{ packages }}"
    state: present
  vars:
    packages:
      - "postgis"

Old, deprecated style

- name: "Install Dependencies"
  apt:
    name: "{{ item }}"
    state: present
  with_items:
    - "postgis"

We now have a technique which allows us to use template files inside of the inventory, instead of declaring the contents of the files as string vars. We should update this role to look for template files in group_vars and host_vars, instead of using the apache_sites var.

We want all applications in the subdomain to be allowed cross domain access.

We are starting to want to run CentOS on servers. We need to update our Ansible roles to work with RPM based distros as well as DEB.