Is there a way to update the .env
files after updating a vault.yml
file without running a deploy?
Or during local development do we need to manually update the .env
file?
Is there a way to update the .env
files after updating a vault.yml
file without running a deploy?
Or during local development do we need to manually update the .env
file?
There’s no built-in way. You could make a custom playbook with that single task if you really wanted to.
In local development you need to re-provision too.
edit: in development a shortcut is doing: ANSIBLE_TAGS=wordpress-install vagrant provision
This topic was automatically closed after 42 days. New replies are no longer allowed.