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
|
@ -15,7 +15,7 @@ I've written scripts to simplify common complex tasks and automated my local dev
|
|||
|
||||
Another main piece of automation I use is to create and manage the infrastructure my applications run in.
|
||||
|
||||
I've talked about it in my [Deploying PHP applications with Ansible and Ansistrano talk](https://www.oliverdavies.uk/talks/deploying-php-ansible-ansistrano), that before you can deploy an application, you need a server with the required packages installed to run it. You may also need a CDN endpoint, SSL certificate, DNS records, CORS policy, database server, container registry, object storage bucket or a number of various other things.
|
||||
I've talked about it in my [Deploying PHP applications with Ansible and Ansistrano talk]({{site.url}}/talks/deploying-php-ansible-ansistrano), that before you can deploy an application, you need a server with the required packages installed to run it. You may also need a CDN endpoint, SSL certificate, DNS records, CORS policy, database server, container registry, object storage bucket or a number of various other things.
|
||||
|
||||
Using automation tools like Terraform, Pulumi or Ansible, you can run a single command to create, update or destroy resources or your entire stack.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue