Remember last week when I mentioned moving the whole server logic from AWS into my Nuxt app? I hoped that it will not cause any issues. Well, it did. 🤦🏻♂️
The current server is configured with 512MB of RAM, but sending the weekly newsletter took more than 1GB of RAM, and my server crashed. I triggered the API endpoint on my local machine to send the newsletter, and it worked fine.
After careful consideration, I decided to move only the email sending process to an AWS Lambda function. This function is triggered by the Nuxt app, ensuring that the app is not hindered by the email sending process. This solution not only provides the server with sufficient resources to handle other requests but also proves to be a cost-effective alternative to upgrading the server. 🚀
👉🏻 In this talk, you get introduced to FormKit — a form-building framework — and how it can empower Vue developers to write consistent, accessible, even delightful forms.
👉🏻 Learn how to create functions that adapt to await usage, enhancing your understanding of Nuxt and empowering you to apply these patterns in your own projects.
Nuxt provides the setResponseStatus composable to set the status code (and optionally the status message) of the response.
This composable only works on the server and will have no effect on the client. Additionally, it can only be used in the Nuxt Context. The Nuxt context is only accessible in plugins, Nuxt hooks, Nuxt middleware, and setup functions (in pages and components).
eventevent will be undefinedundefined in the browser, so you can safely use this composable in your Nuxt context.
In my client's project, I used this composable to set the status code of the response to 410 when a product has expired. This way, the search engines will know that the product is no longer available and will remove it from the search results:
👉🏻 This post dives into the mechanics of Promises, their states (pending, fulfilled, rejected), and how to work with them using the .then() and .catch() methods.
How's it going? I was planning to release the update for Reusable Components yesterday, but things haven't gone as planned. Instead, I will be launching it next week. I need a just a bit more time to make sure that the quality is up to my standards. As I've been updating the course and re-writing all the content and step-by-step refactorings, I've also been able to simplify a few things. It's just like refactoring a piece of code, and it's one of the greatest feelings. I also looked at how much content is in there, and it looks like it will be similar to the Clean Components Toolkit. Lots of great content on how to write highly reusable components, simplified and updated — I can't wait to release the update next week! Oh, and one more thing: I'm doing a podcast with Alex Lichter ! It's called Deja Vue and we'll be releasing the first ...
Monday, November 20, 2023 I'd pay $10K up front # Matt Mullenweg : "Sales of the 100-year plan so far: 0. Hundreds of people filled out the form, though. I think we really messed something up in the follow-up, including not making it self-serve to start. Will review and try again. It's an important promise to us." # I'm very much a customer for this service. It would be worth $10K for to buy 100 years of persistence for my web writing. A simple easy to understand service that helps get the process started. # I transfer scripting.com to Automattic as registrar. # I upload the contents from S3 to Automattic server. Static files, HTML, feeds, images, code. # Automattic provides an API to keep the files updated and so I can add to them as long as I'm still writing. # The files are publicly accessible over HTTP. # Automattic agrees to renew the domain for 100 years, and manage access to the files, with reasona...
评论
发表评论