lamby
runner-images
lamby | runner-images | |
---|---|---|
11 | 51 | |
580 | 9,113 | |
0.3% | 2.9% | |
5.9 | 9.8 | |
3 months ago | 4 days ago | |
Ruby | PowerShell | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lamby
-
Understanding AWS Lambda Proactive Initialization
AWS Serverless Hero Ken Collins maintains a very popular Rails-Lambda package. After some discussion, he added the capability to track Proactive Initializations and came to a similar conclusion - in his case after a 3-day test using Ruby with a custom runtime, 80% of initializations were proactive:
-
💔 Goodbye Cold Starts ❤️Hello Proactive Initialization
This means the Monitoring with CloudWatch is just half the picture. But how much is your application potentially benefiting from proactive inits? Since Lamby v5.1.0, you can now find out easily using CloudWatch Metrics. To turn metrics on, enable the config like so:
-
The Elusive Lambda Console; A Specification Proposal.
After years of smashing Cloud & Rails together, I've come up with an idea. Better than an idea, a working specification! One where us Rails & Lambda enthusiasts can once again "console into" our "servers" and execute CLI tasks like migrations or interact via our beloved IRB friend, the Rails console. Today, I would like to present, the Lambda Console project. An open specification proposal for any AWS Lambda runtime to adopt.
-
The Next Generation of Serverless Is Happening
> Does this mean you have a cron job just pinging the serverless function every 3 minutes? I'm curious how much this adds on to your costs. It means that the whole "don't pay for non-usage" thing is not quite true, but maybe it's still significantly cheaper than running an EC2 instance or whatnot. I'm curious about the cost calculation here.
Yes, specifically it kicks off a Lambda function that does a parallel GET to our website at a special endpoint that has a 100ms "wait" and basic DB call. This keeps the lambda process alive/in-memory.
To keep a function alive costs ~125ms (100ms wait + 25ms full func roundtrip). every 3 minutes. ~0.041% of 1x CPU time. Our website server costs are tiny and lower for Staging and UAT. Benefit - can scale to 1000x (AWS Limit) servers at the speed of your cold start time.
> Another thing I'm curious about, since you have a container-based deployment, did you compare with Fargate?
Yes we use Fargate for our core product which is built in Rails before containers could be deployed in Lambda. Rails works fine on Lambda[0] but the transition cost wasn't worth it for us. Fargate is great, but as you point out it is expensive if your application isn't a user heavy one like ours. To be highly available, we always have a minimum of 2 online but we're a b2b application so our night usage, 10pm-6am is zero. But I have 2 machines just sitting there. This is why i love Lambda >> Fargate.
Also, scalaing Fargate machines is slow if you get a traffic spike.
[0] https://github.com/rails-lambda/lamby
-
Using Tailscale on Lambda for a Live Development Proxy
If you are curious to learn more about how Rails & Lambda work together, check out our Lamby project. The architecture of Lambda Containers works so well with Rails since our framework distills everything from HTTP, Jobs, Events, & WebSocket connections down to amazing CMD Docker contract. The architecture above at the proxy layer was easy to build and connect up to our single delegate function, Lamby.cmd. Shown below.
-
Ruby on Rails on Lambda on Arm64/Graviton2!
Today I am happy to announce that Lamby (Simple Rails & AWS Lambda Integration using Rack) now demonstrates just how easy it is to use multi-platform arm64 images on AWS Lambda. If this sounds interesting to you, jump right into our Quick Start guide and deploy a new Rails 7 on Ruby 3.2 Ubuntu image to see it for yourself.
-
Rails on Docker · Fly
(I have not actually used this myself). The folks over at CustomInk maintain Lamby, a project to run Rails in a quickly-bootable Lambda environment. Might be worth checking out, if you otherwise do enjoy working with Rails: https://lamby.custominktech.com
- Ruby on Jets: Like Rails but Serverless
- Rails on Lambda with Lamby v4
-
How to make your RoR app infinitely scale?
In any case you can try out https://github.com/customink/lamby which is a gem responsible to allow to run a ror app native on aws lambda.
runner-images
-
Show HN: Managed GitHub Actions Runners for AWS
Yeah this is a good option if you'd like something to deploy yourself! You can also build an AMI from GitHub's upstream image definition (https://github.com/actions/runner-images/tree/main/images/ub...) if you'd like it to match what's available in GitHub-hosted Actions.
With Depot, we're moving towards deeper performance optimizations and observability than vanilla GitHub runners - we've integrated the runners with a cache storage cluster for instance, and we're working on deeper integration with the compute platform that we built for distributed container image builds - as well as expanding the types of builds we can process beyond Actions and Docker, for instance.
But different options will be better for different folks, and the `philips-labs` project is good at what it does.
- GitHub switched to Docker Compose v2, action needed
-
We Executed a Critical Supply Chain Attack on PyTorch
Whoa, there's a lot of stuff in there [1] that gets installed straight from vendors, without pinning content checksums to a value known-good to Github.
I get it, they want to have the latest versions instead of depending on how long Ubuntu (or, worse, Debian) package maintainers take to package stuff into their mainline repositories... but this attack surface is nuts.
[1] https://github.com/actions/runner-images/tree/main/images/ub...
-
Terraform module for scalable GitHub action runners on AWS
I had a similar experience with ARC (actions-runner-controller).
One of the machines in the fleet failed to sync its clock via NTP. Once a job X got scheduled to it, the runner pod failed authentication due to incorrect clock time, and then the whole ARC system started to behave incorrectly: job X was stuck without runners, until another workflow job Y was created, and then X got run but Y became stuck. There were also other wierd behaviors like this so I eventually rebuilt everything based on VMs and stopped using ARC.
Using VMs also allowed me to support the use of the official runner images [0], which is good for compatibility.
I feel more people would benefit from managed "self-hosted" runners, so I started DimeRun [1] to provide cheaper GHA runners for people who don't have the time/willingness to troubleshoot low-level infra issues.
[0]: https://github.com/actions/runner-images
- Apple Silicon (M1) powered macOS runners are now available in public beta
-
macOS Containers v0.0.1
Reminds me: Still waiting for native ARM support on GitHub Actions https://github.com/actions/runner-images/issues/5631
-
Question on using Linux Self Hosted Agents with VMSS
Used https://github.com/actions/runner-images to get the packages needed for Ubuntu 22.04 As the packer requires a builder, I used "null" builder to set it as localhost ref: https://developer.hashicorp.com/packer/docs/builders/null (It was way difficult to figure it out the 1st time) I had to modify the .pkr.hcl file to pick my provisioners. I could not understand the use of /opt/hostedtoolcache folder (which I did later)
- steam run problem after install. missing depedencies
- VM Scale Set in Running Status but Failed Provisioning state...leaving agent jobs queued with "No agents in pool VMSS-Prod are currently able to service this request."
- [HELP] Building Unity WebGL projects in Azure Devops CI/CD pipeline
What are some alternatives?
mrsk - Deploy web apps anywhere. [Moved to: https://github.com/basecamp/kamal]
jellyscrub - Smooth mouse-over video scrubbing previews for Jellyfin.
jets - Ruby on Jets [Moved to: https://github.com/rubyonjets/jets]
paths-filter - Conditionally run actions based on files modified by PR, feature branch or pushed commits
socksify-ruby - Redirect any TCP connection initiated by a Ruby script through a SOCKS5 proxy
json-tidy - Pretty prints JSON from stdin, files, or URLs
bgems - Binary rubygems
changed-files - :octocat: Github action to retrieve all (added, copied, modified, deleted, renamed, type changed, unmerged, unknown) files and directories.
buildah - A tool that facilitates building OCI images.
combine-prs-workflow - Combine/group together PRs (for example from Dependabot and similar services)
dockerfiles - Various Dockerfiles I use on the desktop and on servers.
just - 🤖 Just a command runner