Dan Manges
@dan_manges
Followers
2K
Following
4K
Media
72
Statuses
2K
Building the next generation of CI/CD: @rwx_cloud. Previously built @RootInsurance (IPO) and @braintree ($800M acq)
Columbus, OH
Joined February 2008
GitHub just shocked engineering team budgets with a change to GitHub Actions pricing. For people using self-hosted runners, or runners provided by a third-party, GitHub previously offered their CI/CD control plane for free. This will no longer be the case. Many people using
0
3
8
"People can easily migrate CI elsewhere" – and there's no better place to migrate to than @rwx_cloud . It's the only platform that runs as a DAG with automatic content-based caching. Engineers love the performance and UX.
Its unfortunate for GitHub - Actions has no real moat, so I'm not sure what they think this move will do for them. People can easily migrate CI elsewhere, and it opens up vectors for folks like Graphite (and continues to for GitLab).
1
1
5
Love seeing Jared and GitHub communicating about the roadmap. Although you could wait for GitHub to ship this, or you could get it all now on @rwx_cloud
@ThePrimeagen @jamonholmgren @krisrpdev We know we have work to do in maintaining our own open source surfaces for GitHub Actions (actions, runner-images, starter workflows, toolkits, etc.). That being said, I wanted to address what was discussed and also share what’s next for GitHub Actions: With respect to
0
0
2
Pretty incredible what the team @rwx_cloud is doing here. We use RWX at ClickFunnels, so I'm excited to try this out!
We deleted our Dockerfiles at @rwx_cloud and moved to a better, faster way to build container images.
0
1
3
@dan_manges @rwx_cloud All of our builds use RWX for deploying OCI images now. Definitely a better experience and quite a bit faster than docker, thanks for building this!
0
1
1
This is an amazing step forward in building container images! I’ve said it before, but everyone should checkout RWX to replace their CI/CD provider!
We deleted our Dockerfiles at @rwx_cloud and moved to a better, faster way to build container images.
0
1
3
We deleted our Dockerfiles at @rwx_cloud and moved to a better, faster way to build container images.
2
2
9
Next Monday, @rwx_cloud will be launching the biggest evolution in container technology since the release of Docker’s BuildKit, which is now over 7 years old. Docker changed how applications are deployed. Containers bundle system dependencies with application code, providing a
rwx.com
Two weeks ago, we deleted the Dockerfile for our application, and we deleted the step in our CI pipelines that previously ran docker build.
2
6
18
Bye, Dockerfile. I'm shipping our new container image builder. It's so much faster.
2
1
6
I’m not sure how everybody discusses this without acknowledging the tradeoffs. Database performance isn’t the only consideration.
UUIDs are fine it’s almost certainly not your bottleneck lol
0
0
2
It's easy to solve the problem of status pages not being up-to-date. Just render a graph of traffic to the status page.
0
1
6
I'm considering inverting our pager so that I'll get paged when services are up. That way I can go back to sleep until us-east-1 is back online.
0
0
2
That feeling when you open a PR to review it and notice that your scroll bar is tiny.
1
0
2
Had a minor production issue today after updating containerd from 1.7.27 to 1.7.28. Building infrastructure companies is hard. Many bugs are infrequent enough to go undetected in preliminary testing, but they show up reliably at scale.
2
0
8
I’m sure Google Ventures operates independently, but there’s something funny about them backing a company that siphons revenue from Microsoft largely through an arbitrage opportunity. Impressive execution by the company they backed though.
1
0
4
I’m shocked this was a meaningful amount of bandwidth for Cloudflare to handle.
I really should have given @Cloudflare a heads up before dropping a highly-anticipated 7GB ISO on them, but @dok2001 offered impeccable service at 2am his time to get us sorted. This should be super fast in a second.
1
0
5
I'm surprised by how many startups still choose names that are homophones. Maybe there are more written than verbal references to company names though.
1
0
2
It's really hard to improve your products when you can't even change the email address that you use to send invoices without customers pushing back to the point where you revert.
0
0
2
Contrary opinion: very long function bodies are fine. Scrolling through one massive function can be much easier to comprehend than mentally mapping a bunch of tiny fragmented calls spread across a large number of files.
3
0
6