I'd love to see some more detailed write-up on how to switch to Warpbuild for different tech stacks. I tried a few months ago when the instructions were basically just to change the runs-on type but IIRC it failed with an error around setting up ruby (and caching it?) and there were no clear instructions on how to proceed.
Any such error is a bug. We do have tons of ruby users running 1000s of jobs each hour but maybe we are hitting a corner case with you, I'm sorry that that happened and I'll look into it.
Switching from github actions default runners is exactly a one line change.
Migrating from `actions-runner-controller` with k8s or self-managed VMs could be different based on specific customizations in place. However, we have import flows for the former to directly import the custom containers used in k8s, and an AMI import is coming soon.
There shouldn't be any stack specific behavior, except with caches. We have introduced fast custom caching actions including stack specific instructions in docs [1].
