Use environment-specific URLs instead of
...hard-coded ones
This commit is contained in:
parent
6ca5704c21
commit
1b05e63a20
76 changed files with 91 additions and 91 deletions
|
@ -23,6 +23,6 @@ There are other advantages too - clients or product owners are generally happier
|
|||
|
||||
If you're familiar with the DevOps Research and Assessment (DORA) team, three of their key metrics are deployment frequency, lead time for changes, and time to restore service. All of these are improved by small and frequent releases.
|
||||
|
||||
In my [Deployments with Ansible and Ansistrano talk](https://www.oliverdavies.uk/presentations/deploying-php-ansible-ansistrano), I mention that there is a separate rollback role, but I don't think that I've ever used it.
|
||||
In my [Deployments with Ansible and Ansistrano talk]({{site.url}}/presentations/deploying-php-ansible-ansistrano), I mention that there is a separate rollback role, but I don't think that I've ever used it.
|
||||
|
||||
Because I'm deploying small changes often, it's usually much easier to fix forward than it is to rollback, and knowing this makes me a lot less anxious when deploying changes.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue