Add dynamic OG generation

[zephraph]

Adds an /og route that will render an og card for any given page. /og will render the default, /og/getting-started will render for the getting started page, etc. There's a secondary worker that I've added that runs workers-og at og.alchemy.run to render out the actual og image. This theoretically would be a good candidate to get swapped out for a container and just run playwright to snapshot it when needed.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/sam-goodwin/alchemy@483

commit: bdfe200

[sam-goodwin]

Looks like the website deploy failed because SSR is enabled.

Gotta look into why the build doesn't fail when that happens

[zephraph]

cc @sam-goodwin would be good for you to review this specifically

[github-actions]

🚀 Website Preview Deployed

Your website preview is ready!

Preview URL: https://2a6ae632-alchemy-website.alchemy-run.workers.dev

This preview was built from commit 4643378

---

_{🤖 This comment will be updated automatically when you push new commits to this PR.}

[zephraph]

The logic here needs to be updated. This shouldn't be /og/ it should be something more like og.alchemy.run/.... I don't exactly know how best to get the domain though. @sam-goodwin this is what I was talking about when mentioning it'd be nice to have a config output that didn't require deployment. It's a bit of a chicken and egg situation because you need the config to be able to deploy but you can only get it by doing the deploy?

[sam-goodwin]

Why do we need a subdomain for og images instead of generating at build time?

[zephraph]

Okay, here's what's left:

1. The baseImageUrl in routeData.ts needs to be updated to point at the og worker.
2. The og worker needs to get the development URL treatment.
3. Probably should add some cache control headers or manually use the cache API to ensure the og worker isn't generating the og images every time.