Development environment / auth_salt

[fullyint]

@nlott

is it just editing the vault.yml underneath the development folder?

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

If you want custom variables in the .env file created on deploy, each WP site will create env variables using the wordpress_env_defaults 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