Transition from next.seasket.ch domain to seasketch.org

underbluewaters commented 1 year ago

Current user path to our domain looks like the following for legacy SeaSketch. We point both bare and www subdomain to our javascript client, which then redirects to the homepage if the url doesn't include hash parameters indicating it's a deep link into the SeaSketch client app.

flowchart LR
    F["[oregon,mpatt,mapp].seasketch.org"] -->G["CNAME"]
    G -->H["Gandi web redirect"]
    H -->E[seasketch.org]
    E -->J["A record"]
    J--->B
    A[www.seasketch.org] -->I[CNAME]
    I-->E
    B[Legacy Seasketch JS Client]--> C{#project url?}
    C-->|No| D["/homepage.html"]
    C-->|Yes| B

All DNS records are hosted on Gandi, and most (all?) have a TTL of 3 hours (10800 seconds). It would be nice to move DNS records and web forwarding out of Gandi and on to Route53 or Cloudflare.

Current SSN Deployment for comparison:

flowchart LR
    A["next.seasket.ch"]-->B["Route53 A record"]
    B-->C["Cloudfront/S3 Bucket"]
    C-->D["SSN JS Client"]
    E["api.seasket.ch"]-->F["Route53 A record"]
    F-->G["GraphQL API Server (Fargate)"]

underbluewaters commented 1 year ago

I've probably left some internal services out of these diagrams for legacy which are critical. There's a seainternal domain, task server subdomain, db2.seasketch.org, and the url shortener. These will all have to be addressed.

underbluewaters commented 1 year ago

While something of a hassle, looking at the legacy codebase it doesn't look impossible to just manually change all the hard-coded urls to legacy.seasketch.org.

underbluewaters commented 1 year ago

This is what I'd like the final setup to look like:

flowchart TD
    K["legacy.seasketch.org"] --> B
    F["[oregon,mpatt,mapp].seasketch.org"] -->H["Gandi Redirect service"]
    H -->B
    A[www.seasketch.org] -->I["SeaSketch Next Client"]
    J[seasketch.org] -->I
    L[next.seasket.ch] -->I
    B[Legacy Seasketch JS Client]--> C{#project url?}
    C-->|No| D["/homepage.html"]
    C-->|Yes| B
    I-->|#project or #dashboard url?| B
    G["seasket.ch shortener"]-->B
    D-->|"Links to SSN as latest product"|I

underbluewaters commented 1 year ago

Steps towards migration

[x] ADD #projecthomepage/#dashboard url detection to SSN and redirect clients to legacy
[x] point legacy.seasketch.org at old app server
[x] setup SSL for legacy.seasketch.org
[x] check integration between task server and legacy app server to ensure there won't be problems there
[x] update sign-in-with-google support on www.seasketch.org to support legacy.seasketch.org
[x] Change legacy app server and client code to remove/update hard coded host strings
[x] Add /homepage.html content directing users to SSN
[x] preliminary change-over
- [x] point gandi redirects at legacy.seasketch.org
[x] Make sure auth0 is configured (client, server & dashboard) to support seasketch.org domain
[x] Use an explicit token ISSUER env var rather than const HOST = process.env.HOST || "seasketch.org";. And just use "seasketch.org" (or seasket.ch) to avoid issues latter
[x] Determine if process.env.HOST is used elsewhere and anticipate problems
[x] Update SSN to anticipate being referenced from bare seasketch.org
- [x] CDK domain references
- [x] hardcoded next.seasket.ch
- [x] github secrets
- [x] Env vars that need changing:
  - [x] CLIENT_DOMAIN (server)
  - [x] ISSUER (future server var)
  - [x] REACT_APP_PUBLIC_URL (client, remove!!)
[x] Make sure you can actually deploy new version of CDK stacks like LamdaMailer and make sure HOST is set and used properly
[x] Diff ReactClientStack cdk output with actual deployment
[x] Update SSN homepage to have better content, but also refer to legacy SeaSketch for old projects

underbluewaters commented 1 year ago

Final switch-over checklist:

Prep work

[x] Use page rules to redirect naked domain to www.seasketch.org
Phase One
[x] direct www.seasketch.org to the cloudflare pages deployment

Phase Two

[x] Update cdk infra.ts and change next.seasket.ch to www.seasketch.org.
[x] Deploy stacks SeaSketchMailers (locally) and SeaSketchGraphQLServer (using actions)

Phase Three

[ ] next.seasket.ch urls permanently to www.seasketch.org using https://repost.aws/knowledge-center/redirect-domain-route-53

Verification

[x] Send out some test project and survey invites
[x] Make sure survey and project links in admin interface are correct

seasketch / next