lamby-cookiecutter
lamby-cookiecutter copied to clipboard
🐑🛤 AWS SAM Cookiecutter to Quick Start Rails & Lambda
I am trying to deploy the cookiecutter but cannot figure out how to get past this... I have tried both on my machine and on github actions and I am...
Hi Custom Ink devs, I am going through the lamby quickstart. And I believe I'm encountering an issue because I'm using Apple Silicon. I'll keep looking into it but I...
Attempting to run `sam init --location "gh:customink/lamby-cookiecutter"` and after entering the project name returns the following error ``` Command /tmp/tmpawy2lirz.py not available ... Traceback (most recent call last): File "samcli/__main__.py",...
Ignoring public assets breaks sites using the vanilla cookiecutter config. This change was called for in the thread on this issue https://github.com/rails-lambda/lamby-cookiecutter/issues/43, figured I'd knock it out real quick.
As mentioned in this issue https://github.com/rails-lambda/lamby-cookiecutter/issues/41, the default Rack version ends up breaking upon deploy of the cookiecutter project. Bummer to move it backwards but this should get it sorted...
I followed this guide throughoutly, I even switched between arm amd architecture. https://lamby.cloud/docs/quick-start. However, I got this error when accessing function URL: ``` 2023-10-27T18:32:08.670+07:00 | Executing 'config/environment.Lamby.cmd' in function directory...
Running on macOS Sonoma 14.1.1 within the VS Code Dev Container. Deployed to AWS Lambda without any code changes. Following error appears in CloudWatch when visiting the application URL: ```...
Hi there I am trying to setup the deployment on github actions using Devcontainers. I am receiving the error below: ` Setting DockerBuildArgs: {} for RailsLambda function Failed building function...
I'm getting the following errors in Cloudwatch after deploy and can't get the site to load. ``` /usr/local/lib/ruby/3.2.0/bundler/definition.rb:524:in `materialize': Could not find web-console-4.2.1, capybara-3.39.2, selenium-webdriver-4.10.0, webdrivers-5.3.1, bindex-0.8.1, addressable-2.8.5, matrix-0.4.2, regexp_parser-2.8.1,...
Idea is to have a distinct coachable devcontainer image step in the ci/cd flow. Example: https://github.com/rails-lambda/lamby_benchmark/commit/c3af7728acad23e9f2ae10558ac781d708201bcc