# Deploy Clone Project Files dictionary error

**URL:** https://discourse.roots.io/t/deploy-clone-project-files-dictionary-error/5607
**Category:** trellis
**Created:** 2016-01-02T19:21:09Z
**Posts:** 12
**Showing post:** 2 of 12

## Post 2 by @fullyint — 2016-01-02T20:06:14Z

@jwkicklighter The `dict object` (“dictionary”) in the error message is `wordpress_sites` and the `attribute` it is looking for is [the site header](https://github.com/roots/trellis/blob/97a9c05e3479af370a551682d9a689e6763b5d2f/group_vars/production/wordpress_sites.yml#L3) in that list. Could you check that `salonvoandspa.com` is the site name header in your `wordpress_sites` list? If you have a different header name there, use that name in your deploy command:

```
./deploy production siteheader
```

or

```
ansible-playbook deploy.yml -i hosts/production --extra-vars="site=siteheader"
```

Also consider [this note](https://discourse.roots.io/t/deploy-issue-ansible-1-9-4-composer-not-found/5595/7) about ssh keys with bitbucket. Trellis is set up to connect to Bitbucket using your local machine’s ssh key pair instead of the DO droplet’s keypair, so Bitbucket should have your local machine’s public ssh key. The purpose of this “ssh agent forwarding” setup is so that you don’t have to add extra deploy keys to your private repo – Trellis will just forward your regular ssh agent info through your droplet to Bitbucket to make the connection.

I would also recommend changing your [`web_user`](https://github.com/roots/trellis/blob/97a9c05e3479af370a551682d9a689e6763b5d2f/group_vars/all/users.yml#L19) back to `web` or something other than `root` (then rerun `server.yml` and `deploy.yml`). Otherwise you will probably run into the `Error: YIKES! It looks like you're running this as root` described [here](https://discourse.roots.io/t/deploy-issue-ansible-1-9-4-composer-not-found/5595/4). If you run into trouble after changing `web_user` back, there’s some chance that you’ll need to destroy/rebuild the droplet and rerun with `web_user: web`. I haven’t tested, but I suspect it’s possible that running everything once with `web_user: root` could cause permissions/ownership issues that might not resolve with just rerunning with `web_user: web`.

---

_[View the full topic](https://discourse.roots.io/t/deploy-clone-project-files-dictionary-error/5607)._