Tung Nguyen
Tung Nguyen
Oh I see. So hitting into the aggregated 75GB limit from all the lambda functions across the entire AWS account. A shared Lambda layer would help in that case. Will...
This is pretty neat. Also wondering if tagging the CloudFormation stacks themselves is another approach. Believe that stack tags result in tags propagating to all the resources in the stack....
Generated CloudFormation templates deployed with at least one route: $ ls /tmp/jets/demo/templates/ demo-dev-api-deployment.yml demo-dev-api-resources-1.yml demo-dev-app-jets-public_controller.yml demo-dev.yml demo-dev-api-gateway.yml demo-dev-app-jets-preheat_job.yml demo-dev-app-posts_controller.yml $ ls /tmp/jets/demo/templates/demo-dev-api-gateway.yml /tmp/jets/demo/templates/demo-dev-api-gateway.yml $ The key one is `demo-dev-api-gateway.yml` When...
Thanks for the solution suggestions. Unsure on which one to go with at the moment 🤔 Wondering if there’s any consistency to how other frameworks handle Arrays in POST. Will...
Think the suggested approach is fine.
@JackKelly-Bellroy Thanks for the detailed report. Details of fix in https://github.com/boltops-tools/jets/pull/649 @sam0x17 Thanks for the note also. Updated docs with those cavaets: https://rubyonjets.com/docs/routing/custom-domain/#considerationscavaets
Went through docs for v5 testing and it worked. https://docs.rubyonjets.com/docs/email/previews/ So seems fixed.
Took another look at this. Couldn't reproduce. Guessing/hoping that somewhere between Jets 3.0.22 and 3.2.2, this was fixed. And we can deploy an API app without a `public` folder. Closing...
Jets 5 handles this in another way. A single lambda function is deployed to handle all controller requests. https://blog.boltops.com/2023/12/05/jets-5-improvements-galore/ Closing out
Thinking Jets 5 handles this since there’s only one Lambda function for all controllers. https://blog.boltops.com/2023/12/05/jets-5-improvements-galore/