☁️ Cloudflare - Set Up Worker to Route Rules Page to Next.js Site

[bradystroud]

CC: @JackDevAU @adamcogan

Similar to the SSW Website, we have a few different types of pages (templates).

• Rules
• Categories
• Home
• and a few others...

Option A (recommended) - Strangler Fig - Rebuild 1 templates (e.g. Rules) and get that in prod (using a CloudFlare worker to redirect traffic)
Option B - Big Bang - Rebuild the entire site and then deploy all templates at once

See https://www.ssw.com.au/rules/modernize-your-app/

As discussed with @JackDevAU we want to do Option A - Incremental migration

Description

Set up a Cloudflare Worker to route traffic for the Rules page to the new Next.js site as part of the ongoing migration. This worker will intercept requests to the production URL and point them to the corresponding page on the Next.js site, allowing a gradual migration of pages without impacting the overall site structure.

Acceptance Criteria

• ⚠️ Check if this is going to increase the Azure or Cloudflare bill
• Create a Cloudflare Worker that intercepts requests for the Rules page on the current production URL.
• Configure the worker to redirect or proxy these requests to the Rules page on the Next.js site.
• Test the worker in a staging environment to ensure requests are properly routed to the new Next.js page.
• Deploy the worker to production and verify that the Rules page requests are correctly routed to the Next.js site.
• Monitor for any issues or performance impacts after deploying to production.
• Document the worker setup and configuration for future reference, including steps for adding additional pages as the migration progresses.

🤖