# Define fastcgi vars for roles\nginx\defaults\main.yml

**URL:** https://discourse.roots.io/t/define-fastcgi-vars-for-roles-nginx-defaults-main-yml/10731
**Category:** trellis
**Created:** 2017-10-24T20:49:27Z
**Posts:** 5
**Showing post:** 4 of 5

## Post 4 by @fullyint — 2017-10-25T05:48:17Z

One potential for how this could happen relates to Ansible’s [variable precedence](https://docs.ansible.com/ansible/latest/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable). Suppose you were to have these same variables defined in `group_vars/development/`. Such (unmodified) variables would override your modified variables in `group_vars/all/`. (Any particular group in `group_vars` will take precedence over the `all` group.)

You could search your Trellis files for other conflicting definitions of these vars, potentially even in [temp files](https://discourse.roots.io/t/misconfiguration-of-wordpress-site-names/9609/5). Of course, the values in `roles/nginx/defaults/main.yml` shouldn’t be conflicting because they have the lowest priority.

When working out variable precedence, it is often helpful to temporarily insert a `debug` task into the relevant task file or context, just to ensure you know what Ansible is using for variable values. Example:

```
- debug:
    msg: |
      nginx_fastcgi_buffers is `{{ nginx_fastcgi_buffers }}`
      nginx_fastcgi_buffer_size is `{{ nginx_fastcgi_buffer_size }}`
```

---

_[View the full topic](https://discourse.roots.io/t/define-fastcgi-vars-for-roles-nginx-defaults-main-yml/10731)._