Domain migration

Plan

Change hisports.app to play.spordle.com in production and staging.hisports.app to play.spordle.dev in staging.

The HiSports domains will show a notice that the domain has changed and will also allow the Spordle domains to retrieve local storage to maintain login state.

Timing should coincide with the release of the My Account login.

Timeline

There are only two windows to make this kind of change: Christmas break and April break between hockey/soccer seasons.

Staging to be completed early December

Production to be completed on April 1st, 2024.

Affected Resources

List of hisports.app subdomains in active use and where they’re used.

Will initially use HTTP 307 (temporary redirect) in the short term (to allow for potential rollback if issues are discovered), then convert to HTTP 301 (permanent redirect) at a later date.

 

Type

Before

After

Notes

Load Balancer CNAME

 

Type

Before

After

Notes

Load Balancer CNAME

App

Cloudfront (React)

hisports.app
staging.hisports.app
illinois-staging.hisports.app

play.spordle.com
play.spordle.dev
play.spordle.dev

Soft HTML redirect as a migration page is necessary to facilitate local storage migration

HTTP 307

Prod

Staging
d2m8vmqwaf7b8h.cloudfront.net

API

K8s

api.hisports.app
api-staging.hisports.app

api.play.spordle.com
api.play.spordle.dev

HTTP 307

Prod
a6f010af801214ead919eb75481efa85-61345506ccba69a1.elb.ca-central-1.amazonaws.com

Staging
a8a4b439bbd564350bad198cb54c4a23-8080c14a797c0cdd.elb.ca-central-1.amazonaws.com

Reports (PDF)

Lambda (PDF)

pdf.hisports.app
pdf-staging.hisports.app

pdf.play.spordle.com
pdf.play.spordle.dev

HTTP 307

 

Reports (React)

Netlify (React)

reports.hisports.app
reports-staging.hisports.app

reports.play.spordle.com
reports.play.spordle.dev

HTTP 307, but not user-facing

 

Metabase

K8s

metabase.hisports.app
metabase-staging.hisports.app

metabase.play.spordle.com
metabase.play.spordle.dev

HTTP 307

 

Files

S3

files.hisports.app
files-staging.hisports.app

files.play.spordle.com
files.play.spordle.dev

HTTP 307? S3 buckets, not sure what’s possible

 

Calendar

Lambda (API)

go.hisports.app
go-staging.hisports.app

go.play.spordle.com
go.play.spordle.dev

HTTP 307.

Could rename this, only used for calendar lambda.

 

Scorekeeper Guide

Netlify (React)

help.hisports.app

Confluence

HTTP 307 to Confluence?

 

Other

Cloudflare

Cloudflare

K8S

cache-api.hisports.app

logos.hisports.app

grafana.hisports.app

api-cache.play.spordle.com

logos.play.spordle.com

grafana.play.spordle.com

HTTP 307; need to communicate change to Page team

No idea where logos domain is used

HTTP 307; internal use

 

Email

MX

m.hisports.app
m.staging.hisports.app

m.play.spordle.com
m.play.spordle.dev

Potential email delivery issues due to domain change?

 

Things to confirm

Email configuration on Spordle domains (SPF, DKIM, DMARC)
AWS TXT records
Email deliverability
S3 bucket redirect