Open amankumarrr opened 1 month ago
@wicksipedia @SSWConsulting/ssw-website-maintainers
@chrisschultzssw and I have successfully placed Cloudflare in front of Front Door for our staging domain tfs365.com. We've observed a significant improvement in page speeds, thanks to Cloudflare's caching capabilities.
Here are the comparisons:
Figure: Page speed insights for mobiles
Figure: Page speed insights for mobiles
@wicksipedia @SSWConsulting/ssw-website-maintainers
Impacted Routes:
Unimpacted Domains from Front Door:
⚠️ Note: Once we place the /ssw
route on Cloudflare as a trigger for our worker, v1 will not be accessible afterwards. Ideally, we should do this once we are confident enough to turn off the VM.
@SSWConsulting/ssw-website-maintainers
I'm currently blocked on completing the remaining redirects since @chrisschultzssw needs to plan the migration for ssw.com.au. According to my conversation with him this morning, he anticipates being able to handle this planning and migration later this week.
@wicksipedia @bradystroud
We are currently blocked. As discussed with @chrisschultzssw , he needs to get @ozdemir-mehmet’s approval on the migration plan. If he’s satisfied with it, we will likely proceed with the migration on Monday.
I have created a rule for the redirects - https://www.ssw.com.au/rules/handle-redirects/ and modified this rule for the CDN - https://www.ssw.com.au/rules/do-you-use-cdn-for-js-files/
@chrisschultzssw
I have created a new issue for the remaining domains - https://github.com/SSWConsulting/SSW.Website/issues/2781
As per my conversation with @wicksipedia and @chrisschultzssw, we are going to place Cloudflare in front of Front Door. We will be testing this on the tfs365.com domain and, upon successful testing, will roll it out to production. This approach aims to reduce downtime during the DNS cutover and ensure a smooth migration from Front Door to Cloudflare.
Tasks: