# Development environment / auth_salt

**URL:** https://discourse.roots.io/t/development-environment-auth-salt/10415
**Category:** trellis
**Created:** 2017-09-13T17:50:04Z
**Posts:** 6
**Showing post:** 2 of 6

## Post 2 by @fullyint — 2017-09-13T19:12:07Z

> [@nlott](#):
>
> is it just editing the vault.yml underneath the development folder?

:white_check_mark: yes (under `env` within `vault_wordpress_sites`)

> [@nlott](#):
>
> Is there anything I need to do aside from restarting my vagrant instance to get these to be recognized?

No Vagrant restart needed to apply changes to `.env` file.

- For Vagrant dev, need to run `wordpress-install` role:  
`ANSIBLE_TAGS=wordpress-install vagrant provision`

- For staging and production, just redeploy

A few related links for background:

> [@Custom env variables trellis](https://discourse.roots.io/t/custom-env-variables-trellis/6330/2):
>
> If you want custom variables in the .env file created on deploy, each WP site will create env variables using the [wordpress\_env\_defaults](https://github.com/roots/trellis/blob/fc44e94d6f174792b00833d79a89dd92d4b1daf8/deploy.yml#L16-L23) from deploy.yml. To override or add to these env variables, you can edit group\_vars/\<environment\>/wordpress\_sites.yml. For example, if for example.com you wanted to override the default db\_name and add a new var new\_env\_var, you could add this for the site example.com: wordpress\_sites: example.com: ... env: db\_name: override\_name new\_env\_var: fo…

[https://discourse.roots.io/t/connect-to-mysql-using-sequel-pro-when-there-is-already-a-mysql-in-local/9409/6](https://discourse.roots.io/t/connect-to-mysql-using-sequel-pro-when-there-is-already-a-mysql-in-local/9409/6)

---

_[View the full topic](https://discourse.roots.io/t/development-environment-auth-salt/10415)._