[FEATURE]: ensure production domain works

[slackermorris]

I am having an issue.

[slackermorris]

Remember, deployment to production worked from the CLI:

I will check the deployment logs in Github Actions.

[slackermorris]

I mean this doesn't look correct:

All my UI code is referring to the staging API when in fact the production url has a different alias.

api-production.badreviewsmakegoodmovies.com

[slackermorris]

The question is how to tell what stage/environment I am in.

[slackermorris]

It will pay to read this: https://arc.net/l/quote/eaowetpt

[slackermorris]

Alright just got to rinse and repeat.

[slackermorris]

Nope. The above change had nothing to do with nothing, lol.

I guess I need to form a better mental model of how the website is being server.

[slackermorris]

I'll look at the recommended deployment docs from Astro's side of things:

• https://docs.astro.build/en/guides/deploy/aws/

[slackermorris]

I am having a look at the SST Console to determine what the issue is.

[slackermorris]

Let's see what it logs out on development.

Local http://localhost:4321 returns / for the path:

What should I do?

I need to determine where and why this code executes.

Maybe related? https://github.com/withastro/astro/issues/4190 I literally have the worst mental model w/r/t this whole side of things. Perhaps I am best clearing that up before going any further.

[slackermorris]

Hmm. Perhaps I missed something?

I added this and redeployed to production. So, let's see.

[slackermorris]

I need to read this at some point:

[slackermorris]

Here are all my application code assets: https://ap-southeast-2.console.aws.amazon.com/s3/buckets/production-bad-reviews-make-g-sites3bucket2b2851f3-e7hiz9cmz07z?region=ap-southeast-2&bucketType=general&prefix=_astro/&showversions=false

[slackermorris]

Here are the CloudWatch logs for the problematic lambda: https://ap-southeast-2.console.aws.amazon.com/cloudwatch/home?region=ap-southeast-2#logsV2:log-groups/log-group/%2Faws%2Flambda%2Fproduction-bad-reviews-ma-siteServerFunction6DFA6F-M4nOH2mHWP5j

[slackermorris]

I have all my notes in Obsidian. The rub is: bumping to the most recent version of Astro seems to have solved the issue.