[FEATURE]: add integration with Letterbxd API

[slackermorris]

https://api-docs.letterboxd.com/

[slackermorris]

This is the endpoint that I am intending to hit:

• https://api-docs.letterboxd.com/#:~:text=/-,films,-A%20cursored%20window

[slackermorris]

It seems for each request that I have to create a salted string and sign the request with it:

• https://debugpointer.com/javascript/create-sha256-hash-with-salt-in-javascript
• https://api-docs.letterboxd.com/#signing:~:text=a%20new%20token.-,Request%20signing,-All%20API%20requests

[slackermorris]

Perhaps I can use this to hardcode the values before I install any dependencies to manage the same salting:

• https://emn178.github.io/online-tools/sha256.html

[slackermorris]

I need access to the API. If I don't get it then I will have to parse the RSS feed. Yikes.

• https://www.reddit.com/r/Letterboxd/comments/ht1xc5/letterboxd_api/

[slackermorris]

The API is in beta. I need to request access to it. Alternatively, I can export and import my data using CSV. This truly might be my only option.

Read Path

I would have to make an export of my data. It's gzipped so I would have to unzip it and then file search it. Since I don't have access to the API I would have to perform this action via a headless browser or something similar.

Write Path

I would have to do the above in reverse. This would be hugely problematic. Again, I'd have to use a headless browser or equivalent.

Something like an on demand headless browser that assumes my credentials and logs into Letterboxd and performs the relevant actions. This seems a little strange.

[slackermorris]

I am thinking that it might be more beneficial to stand up my own datasource. Likely using a Serverless Stack.

I guess one of my questions at the moment will be whether or not I want to include this code in my existing astro project or not.

1. Can I use Astro with the AWS SDK?

Yeah, it feels like it would be way easier to stand a Serverless Stack project up and just expose endpoints off it.

[slackermorris]

This might not be relevant, but it seems interesting:

• https://www.jerrychang.ca/writing/building-the-astro-lambda-at-edge-adapter
• https://github.com/aws-amplify/amplify-ui/issues/3206

[slackermorris]

For this to work I likely have to enable SSR as well. I think this requires installing an adapter.

• https://docs.astro.build/en/guides/server-side-rendering/
• https://www.freecodecamp.org/news/how-to-use-the-astro-ui-framework/#chapter-6-server-side-rendering-ssr-in-astro-1
• https://www.youtube.com/watch?v=aIHRjloFASU

Yeah, the content is dynamic. There is no way that I can use SSG for this.

I should be making use of SSR adapters. Or a different framework.

• https://docs.astro.build/en/guides/data-fetching/#:~:text=Your%20deployed%20Astro%20site%20will%20fetch%20data%20once%2C%20at%20build%20time.%20In%20dev%2C%20you%20will%20see%20data%20fetches%20on%20component%20refreshes.%20If%20you%20need%20to%20re%2Dfetch%20data%20multiple%20times%20client%2Dside%2C%20use%20a%20framework%20component%20or%20a%20client%2Dside%20script%20in%20an%20Astro%20component.

[slackermorris]

Regardless of whether I can use the aws-sdk in the current Astro project or not, those resources I am interfacing with need to be on AWS somehow. So, my best bet is to write my own backend. I'll use a Serverless Stack.

[slackermorris]

Lol, this is the exact adapter I need:

• https://docs.sst.dev/start/astro

Drop a deployment solution (Serverless Stack, AWS) into your chosen framework

It scaffolds a monorepo. We can write serverless functions.

[slackermorris]

This is a tutorial that involves building a SST project:

• https://blog.logrocket.com/build-full-stack-serverless-app-sst/

[slackermorris]

I think it will be a good idea to review the permissions specified here.

TBH I think this is a whole other thing to be done. I need to pull my head around IAM policies. I think once I do this that using something like this: an analyser of AWS activity to determine policies for a user, would be the best thing to use.

Also, refer to this, perhaps set up a DynamoDB and try to set an item into it.

[slackermorris]

We have deployment.

[slackermorris]

I should stand a Dynamo table up. See how it feels. I think it is really important to better understand DynamoDB and how it works to leverage how it stores data.

[slackermorris]

This is what I am referring to.

[slackermorris]

This was really helpful for setting the table up. But I think I need something a little more bespoke Astro (setting shit in front matter, etc).

This gives a better explanation of why this project structure is employed.

[slackermorris]

Hmmm. It seems like my project structure is a bit amiss.

SST and Astro tutorial.

[slackermorris]

Actually, I don't think I need to make any changes. As per.

Ahhh 👇. I see now.

[slackermorris]

I am referring to this.

https://pieg1bg8t8.execute-api.ap-southeast-2.amazonaws.com

[slackermorris]

I got the table stood up.

[slackermorris]

I think I need to get rid of the bottom two resources. I don't deploy this to this region anymore. It is an artefact of first deployments.

[slackermorris]

This is how to read from Dynamo using a Lambda we have written in the packages > fns directory. Then I'm not sure how Astro can consume this endpoint.

I wonder if we can use the aws-sdk > DynamoDB client directly in the front matter of the Astro pages?

[slackermorris]

There is potential here to integrate ElectroDB. But I think I should consider this someplace else down the line.

[slackermorris]

I really need to review the "Architectural Section" of this video to better understand what is happening here.

This is also a great resource.

[slackermorris]

This helped me to understand how to test lambdas locally.

[slackermorris]

This is what I am using to create the POST endpoint for creating a user.

I'll then need to integrate this with the Astro project. I think I can make a call to the endpoint in the front matter.

[slackermorris]

I had all my .sst files checked in.

This helped me confirm that they shouldn't be.

[slackermorris]

This is handy but it is super outdated as well.

[slackermorris]

These two are equivalent when recommending how to add consume DynamoDB in a lambda handler.

• https://sst.dev/chapters/add-an-api-to-create-a-note.html
• https://github.com/sst/examples/blob/main/crud-api-dynamodb/src/create.js

[slackermorris]

What is npx sst dev used for?

What is sst bind used for?

[slackermorris]

I would really like to clear up the scripts section. Get things to run as pre scripts/sequentially.