Closed amankumarrr closed 3 weeks ago
For newsletter asset redirects please see link at https://github.com/SSWConsulting/SSW.Website/issues/2617#issuecomment-2136275918
@wicksipedia @SSWConsulting/ssw-website-maintainers
Redirects Status for tfs365.com (Staging site) Domain:
All redirects (total of 1,026) have been tested and added successfully for the following routes:
✅ legacy-redirects ✅ case-studies ✅ consulting ✅ events ✅ static ✅ archive ✅ Website-redirects ✅ Newsletters content
Remaining Redirects to be Implemented:
For the following domains, redirects are still pending:
❌ dory-redirects.json: Redirects for the sswdory.com
domain are yet to be set up.
❌ prod-dotcom-redirects.json: Redirects for the ssw.com
domain are not yet implemented.
❌ staging-dotcom-redirects.json: Redirects for the staging.ssw.com
domain are pending.
Here is the repo - https://github.com/SSWConsulting/SSW.Cloudflare
Download this to view the result - https://github.com/SSWConsulting/SSW.Cloudflare/blob/main/test-scripts/url_redirect_report.html
@wicksipedia @chrisschultzssw @bradystroud @andrewwaltosssw @Calinator444
As we are unblocked now to move forward with this task, we need to add worker routes for ssw.com.au
in order to soft-turn off the VM.
Note: If we implement the route, our website v1, will not be accessible at all from /ssw
.
Tasks:
@amankumarrr I ran the URL redirect status report and I noticed a number of the redirects for /archive
were returning 403s or 421s (806 pages affected)
Is this expected behaviour?
Figure: 400 level responses for archive pages
Nevermind, just tried rerunning the build and deploy workflow https://github.com/SSWConsulting/SSW.Cloudflare/actions/workflows/main.yml
In the past 24 hours, these are stats for Cloudflare on route /ssw/*
Figure: Stats from Cloudflare
@wicksipedia @jeoffreyfischer
We can add redirects logs in App Insight.
Figure: Logs in App Insight for redirects from worker
@jeoffreyfischer
Hey @wicksipedia ,
Could you please review the plan for implementing redirects through the Worker?
In the attached screenshot:
Figure: Plan for the redirects and moving away from Front Door
As per my conversation with @wicksipedia, I will improve the drawings and discuss the plan with him and @amankumarrr on Friday.
As per our conversation with @wicksipedia and @amankumarrr, the Cloudflare migration will be performed in 2 steps:
Before pushing Step 1 to Prod, @amankumarrr will update the README and make a Done Video about how to use Cloudflare. This is to ensure that anyone can use it.
About Step 2, @amankumarrr and @jeoffreyfischer will investigate several FREE options and then discuss with @wicksipedia about which one we will go with.
Screenshots
Figure: Step 0 - Current workflow
Figure: Step 1 - Transition workflow
Figure: Step 2 - Final workflow
As per my conversation with @wicksipedia and @amankumarrr, I have investigated some CDN options:
https://developers.cloudflare.com/workers/platform/limits/
FREE (paid options available)
https://cloud.google.com/cdn/pricing
Pay by usage
Not Found
https://www.fastly.com/pricing/
Lowest Tier: 1500$/month
Below are the total monthly hits in June 2024 on:
Screenshot
Figure: Monthly hits count on SSW Website, rules, people and archive
As per my conversation with @wicksipedia , I have investigated the limits for a $5/month plan with CloudFlare. ✅ All lights are green. ⚠️ The only slight warning is about the Routes (see below).
Requests | Price | Likelihood on SSW Website |
---|---|---|
10 million | $5/month | High |
20 million | $8/month | Medium |
50 million | $17/month | Low |
Table: Projection (if we ever exceed the 10 million requests cap)
@wicksipedia
We exceeded the request limit when the Cloudflare worker went live on production.
Had a look through the pricing doc. If we were to switch to the standard pricing plan our limit would increase to 10 million requests per month (or approximately 333,0000 requests per day over the previous 100,000)
I've included the pricing model below
In the previous comment, I've pointed out that the current number of requests on SSW Website is about 9.5 millions/month. So I recommend going for the 8$/month plan to allow for a maximum requests number of 20 million/month.
Figure: SSW Monthly requests + Cloudflare pricing plan (copied from previous comment)
We can't push this into prod until the purchase please gets approved.
See email - Purchase Please - Request for Cloudflare workers standard (⚠️ High priority)
@wicksipedia
The purchase please has been approved and the Cloudflare worker is now in production. (You can test the redirects at ssw.com.au/archive in the left hand side)
@chrisschultzssw said he was going to add a billing alerts just in case we exceed the estimate of $146.45 per year.
I also added a staging workflow for testing redirects before pushing to prod. The done video for that is below (same as the done video I did in the PBI this week)
@chrisschultzssw said he was going to add a billing alerts just in case we exceed the estimate of $146.45 per year.
Done.
Description: We need to add redirects for all /archive from v1 to our new routes on Azure storage containers.