Reactive-Resume VS Previous Serverless Version 0.5.x

Go to App | Docs

Yo ocupo uno de los de Reactive Resume

So I would like to use an updated version of Reactive Resume. Currently the community app is stuck at v1 whereas the app has reached v4.

Just installed with docker with this and it works great. https://github.com/AmruthPillai/Reactive-Resume/blob/main/tools/compose/simple.yml

Hi! Recently updated my CV myself, and used this website: https://rxresu.me/

Just wanted to mention this here. You don't need a PC with lots of resources these days. Anything that can run a browser can also be used to edit images, create graphics, or even resumes. I think with those tools, you could even use a crappy library PC as long as it has a modern browser running.

Github | Website

i deployed a lambda and http api gateway using a serverless.com (sls) template as a start. I get the following error when it processes a specific request:

Have you tried serverless.com ? It lets you have infrastructure as code.

- With Lambda, you manage creating and building the container yourself, as well as updating the Lambda function code. There are tools out there such as sst or serverless.com which help streamline this.

If you'd like to use Lambda, usually you need to engineer FOR it, from day one, you don't (often) get to choose some other framework and shoehorn it into Lambda and Serverless. There's some great frameworks to help deploy code into Lambda easily and create REST endpoints for things, one such frameworks is serverless.com that helps easily deploy to it, but it lacks a framework for doing REST that also supports local emulation (as easily). For that, I recommend a framework by AWS called Chalice. This is an amazing REST framework that runs a proxy that works locally and deploys exactly the same on Lambda, it is Python however.

I use serverless.com for AWS stuff.

After knocking out a README with a set of goals and a list of TODOs to check off as I made progress, I spent about 10 hours over a weekend trying to get something to work. I used serverless for making Lambda easier, Github Actions for the deploy pipeline and store my credentials; and sadly I rolled my own access_token refresh logic because I couldn't find a helper that just did that for me! wtf!?

Does everyone who uses Workers just use wrangler cli and the cloudflare console UI for everything or is anyone using other tools like serverless framework (https://serverless.com) instead? Looks like they added some support for cloudflare but haven't tried it yet.