Add daily email for 2024-12-27
How quickly can you create a new environment?
This commit is contained in:
parent
dbe1323c0b
commit
3100b7b4c2
36
source/_daily_emails/2024-12-27.md
Normal file
36
source/_daily_emails/2024-12-27.md
Normal file
|
@ -0,0 +1,36 @@
|
|||
---
|
||||
title: How quickly can you create or update an environment?
|
||||
date: 2024-12-27
|
||||
permalink: daily/2024/12/27/quick
|
||||
tags:
|
||||
- software-development
|
||||
cta: ~
|
||||
snippet: |
|
||||
If you needed to update an environment for your application, or create a new one from scratch, how easy would that be?
|
||||
---
|
||||
|
||||
A common reason why environments aren't updated and get out of sync is because it's a time-consuming or complex task.
|
||||
|
||||
The process should be simple to run, quick, reliable and reproducible.
|
||||
|
||||
It's the same as deploying a change to a staging or production environment.
|
||||
|
||||
You want the same result on every time on every environment.
|
||||
|
||||
You want every environment - including [local development environments][2] to be as consistent as possible to minimise bugs and errors.
|
||||
|
||||
To do this, I automate things to make them as simple as possible.
|
||||
|
||||
I use [run files][0] with commands to import databases, perform updates and run pre-update and post-update tasks.
|
||||
|
||||
I use tools like Nix and [devenv][1] to create identical and reproducible environments.
|
||||
|
||||
The simpler and quicker is it, the more it can and will be done.
|
||||
|
||||
You can also use automation to perform long or complex tasks outside of working hours such as sanitising and importing large databases.
|
||||
|
||||
The more you can automate, the better.
|
||||
|
||||
[0]: {{site.url}}/daily/2022/08/15/using-run-file-simplify-project-tasks
|
||||
[1]: {{site.url}}/daily/2024/11/11/could-nix-and-devenv-replace-docker-compose
|
||||
[2]: {{site.url}}/daily/2024/12/25/localhost
|
Loading…
Reference in a new issue