opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

Add daily email for 2024-04-02

Browse source 
Releasing a new project one page at a time
This commit is contained in:
Oliver Davies 2024-04-04 22:27:04 +01:00
parent d78e7a8001
commit e3ccde801f
1 changed files with 27 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

27
source/_daily_emails/2024-04-02.md Normal file
View file

@ -0,0 +1,27 @@
---
title: Releasing a new project one page at a time
date: 2024-04-02
permalink: archive/2024/04/02/releasing-a-new-project-one-page-at-a-time
tags:
- software-development
- drupal
cta: ~
snippet: |
How do you release a new website? One page at a time.
---
How do you release a new project?
Do you build everything and release everything at once?
I've used the strategy of building and releasing it a page at a time and running two versions simultaneously.
The main live version stays running, and you use a tool like NGINX or Cloudflare as a gatekeeper to direct traffic to the correct application - either the current one or the new one - based on the requested page.
When a page is ready, you add it to the list of pages to serve from the new application to put it live.
If there's an issue, it is also easy to revert to the original page.
I've used this approach with my website and for client Drupal upgrade projects, where some pages are on Drupal 7 and some on Drupal 10.
It's not the right approach for every situation, but it's a useful one to have in the toolkit.