# Diving into Trellis, Running a fresh unchanged config

**URL:** https://discourse.roots.io/t/diving-into-trellis-running-a-fresh-unchanged-config/5935
**Category:** trellis
**Created:** 2016-02-14T16:12:22Z
**Posts:** 7

## Post 1 by @daadir — 2016-02-14T16:12:22Z

Please help me understand this… :footprints:

Catching up on the great work done here, im giving this a go on windows, with babun, zsh.  
Some things / questions / wonders arise.

Here’s what i did:

- Cloned trellis/master into Trellis directory

- Cloned Bedrock into site directory

- cd into trellis \<-- missing from docs

- Ran vagrant up [ansible should run on the VM when host is windows]

- \*Unchanging default values for a first time run, since i want to first see i get how this comes together.

- Good. :kissing_closed_eyes:  
Hat off - the site loads and runs fine, albeit a bit **slower** than another vagrant box i have on the same laptop. [pages take 2-3 seconds to load on the trellis provisioned box, as opposed to \<1sec on a vvv provisioned one :confused:]

* * *

1. Why daemonize ? What is it’s purpose here, and do i now find any mention to it in the repo ?

2. I get a few red lines from vagrant up / provision

Errors:

```
==> default: dpkg-preconfigure: unable to re-open stdin: No such file or directory

==> default: TASK [wordpress-setup : Template files out to includes.d] **********************
==> default: /bin/sh: 1: cd: can't cd to /vagrant/roles/wordpress-setup/templates/includes.d
```

3 . Even though i can ssh just fine into the box, i get the ssh-forwarding note - why?  
I followed the [GitHub guide](https://help.github.com/articles/working-with-ssh-key-passphrases/#auto-launching-ssh-agent-on-msysgit) although i am not sure i needed to, as i was able to login to other vagrant boxes without it, and also make scp requests to other servers on the nets…

* * *

4 . Ansible does something even though nothing changed in the config files? ;

from `vagrant up`:

```
==> default: PLAY RECAP *********************************************************************
==> default: 192.168.50.5 : ok=97 changed=73 unreachable=0 failed=0
```

+From `vagrant provision` a few minutes later:

```
==> default: PLAY RECAP *********************************************************************
==> default: 192.168.50.5 : ok=88 changed=2 unreachable=0 failed=0
```

+From _another_ `vagrant provision`:

```
==> default: PLAY RECAP *********************************************************************
==> default: 192.168.50.5 : ok=88 changed=1 unreachable=0 failed=0
```

^ This will be the output for any following run.

1. How is it the task count don’t add up?
2. Where is the `1 changed` from ?

Many questions but this system does make me ask them…  
I am going to try some more tests now. Would extremely appreciate any light you can shed on these issues.

Thanks much!

---

## Post 2 by @swalkinshaw — 2016-02-15T04:56:58Z

1. `daemonize` is a dependency of the `mailhog` role that we pull in from Ansible Galaxy. That’s why you don’t need any reference to it in our codebase :). If you did `grep -r 'daemonize' .` (on the VM in your case) then you’d see it.

2. I haven’t seen that message before. If you do any further debugging please let us know.

3. I believe that warning is there because deploys need SSH forwarding. It doesn’t matter for development though. Maybe the message could be improved. /cc @QWp6t

4. You’re right that `changed` should be `0` on subsequent provisions. I believe there’s 1 or 2 bugs in core Ansible modules which causes this problem. There isn’t much we can do unfortunately until it’s fixed upstream.

---

## Post 3 by @QWp6t — 2016-02-15T10:05:38Z

Yeah, the SSH forwarding note is there in case you want to provision a remote server or deploy to one. You probably won’t be able to do that without proper SSH forwarding.

---

## Post 4 by @daadir — 2016-02-15T20:32:44Z

Thanks that helped.

For using a different MTA, woulnd have to change requirements.yml, and get roles for that one, right?

What output is expected from `ls -la /vagrant/roles/wordpress-setup/templates/includes.d` on a freshly provisioned box?  
`roles/wordpress-setup/nginx.yml` refers to `templates/include.d/` and tries to cd into it, but it ain’t there…

Thanks for commenting @QWp6t  
One thing is the message is injected to .profile on each provision i end up with quite a few :stuck_out_tongue: mentions to a link that doesn’t actually fix the issue. :eyes:

Moreover, now initial page wait for each page load is up to 5 seconds !

---

## Post 5 by @fullyint — 2016-02-16T06:32:44Z

@daadir The `includes.d` directory is optional, for when you have [Nginx includes](https://roots.io/trellis/docs/nginx-includes/). The `|| :` at the end of the [command](https://github.com/roots/trellis/blob/904587996849cc8397e7eb289de9701e8c59c362/roles/wordpress-setup/tasks/nginx.yml#L22) `cd <includes.d path> && <do stuff> || :` causes the command to still return a `0` (non-error) exit status when `includes.d` is missing, so the playbook won’t fail/halt.

The Nginx includes feature was developed with Ansible 1.x, which didn’t print the `can't cd to...` message, but Ansible 2.x does. The next revision of the Nginx includes feature could switch some of those tasks to run only when `includes.d` is present, avoiding the error and the message. In the meantime, you can just ignore the message.

As for the `dpkg-preconfigure` error you mentioned in your original post, it looks like there are a number of google results, which perhaps you’ve explored already.

---

## Post 6 by @daadir — 2016-02-16T18:00:07Z

@fullyint - Where should one look for include playbooks to use or learn from?

@swalkinshaw my load looks like so:

 ![](https://discourse.roots.io/uploads/default/original/2X/8/85799250fde8c7e0e4361c903384418224e56166.jpg)

if the box just came up now, it would take 2-3 seconds of wait for served resources. If its running longer, it could  
take 6 seconds of initial wait time. I tried this also with twenty fifteen, its the same - why like this?  
Is there a good way to test where the slooowness is coming from?

---

## Post 7 by @fullyint — 2016-02-16T18:21:17Z

> [@daadir](#):
>
> Where should one look for include playbooks to use or learn from?

The Nginx includes feature is for including conf files into your site’s Nginx conf [here](https://github.com/roots/trellis/blob/904587996849cc8397e7eb289de9701e8c59c362/roles/wordpress-setup/templates/wordpress-site.conf.j2#L58). I’m not aware of examples out there. I’ve used it once to include some redirects. I created a list variable like this in `group_vars/all/main.yml`:

```
redirects:
  - from: slugtoredirect
    to: http://othersite.com/newslug/
  - from: anotherslug
    to: http://someothersite.com/anotherslug
```

Then I created this template in `roles/wordpress-setup/templates/includes.d/example.com/redirects.conf.j2`:

```
# {{ ansible_managed }}

{% for item in redirects | default([]) %}
  location ~* /{{ item.from }}/? {
    return 301 {{ item.to }};
  }

{% endfor %}
```

You’ll be able to figure out anything you need with the example above, the [Nginx docs](https://roots.io/trellis/docs/nginx-includes/), the [Jinja templating docs](http://jinja.pocoo.org/docs/dev/templates/), [Ansible docs](http://docs.ansible.com/ansible/index.html), and google. Enjoy.