Add daily email for 2024-04-03
Switching web servers using Build Configs
This commit is contained in:
parent
e3ccde801f
commit
3e1bb141c5
25
source/_daily_emails/2024-04-03.md
Normal file
25
source/_daily_emails/2024-04-03.md
Normal file
|
@ -0,0 +1,25 @@
|
||||||
|
---
|
||||||
|
title: Switching web servers using Build Configs
|
||||||
|
date: 2024-04-03
|
||||||
|
permalink: archive/2024/04/03/switching-web-servers-using-build-configs
|
||||||
|
tags:
|
||||||
|
- software-development
|
||||||
|
- build-configs
|
||||||
|
cta: ~
|
||||||
|
snippet: |
|
||||||
|
Today, I used my Build Configs tool to easily switch a project from one web server to another.
|
||||||
|
---
|
||||||
|
|
||||||
|
Have you been in a situation where you needed to switch something in a project, like the type of database or a payment provider?
|
||||||
|
|
||||||
|
Today, I decided to switch a project from NGINX to Apache.
|
||||||
|
|
||||||
|
Usually, this would involve using a different base Docker image, creating new configuration files, and changing things like the root directory for my project.
|
||||||
|
|
||||||
|
But, because I'd built this into [Build Configs], I was able to change a few lines in one file, and when I re-generated the configuration files, this project was running Apache.
|
||||||
|
|
||||||
|
This is an excellent example of why I built this tool: to save time and reduce duplication across my projects.
|
||||||
|
|
||||||
|
For this change, it did both.
|
||||||
|
|
||||||
|
[build configs]: {{site.url}}/talks/building-build-configs
|
Loading…
Reference in a new issue