Mobile CI providers know this, and they are expanding their offerings with solutions that could be just CLIs, playing a game of making their customers believe that it'd be costly to leave their setup, but it's not. It's getting cheaper and cheaper. Lastly, Dagger offers a wake-up call, helping you realize that you can create automation that's not tied to a specific CI provider's proprietary steps or YAML pipelines. You can loosely depend on them, making your automation portable. Virtualization is becoming commoditized with solutions like Tart, Lume, and Curie, many of which have permissive licenses. This is attracting a stream of contributors aiming to create a top-notch virtualization tool comparable to Docker, within the limitations of the OS. Simultaneously, more cloud providers, such as MacStadium, AWS, and Scaleway, are offering macOS environments as a service. Some are more productized than others, yet all provide an API to request a Mac Mini with specific specifications. This option did not exist before. Git forges like GitHub, GitLab, and Forgejo offer seamless integration for code collaboration while allowing you to bring your own hosts. Companies such as Cirrus Labs, Cirun, and Depot can supply these hosts if you prefer not to manage them yourself. The mobile #CI space is plateauing, and we might be on the verge of a DevX innovation in mobile tooling. Let me explain why. 
Really? That seems like an unlikely reason. The signature just verifies the commit data minus the signature, it shouldn't matter what is in there for a verification. Can you point me at a use case? In fact, if this were true, Gitea would break with any new future official git headers.
Register to attend our team's workshop at @cloudnativegeo.org! The workshop will teach attendees how to use the @zarr.dev data format model for cloud-native geospatial datacube analysis.
🗓️ Apr 30-May 2
📍Snowbird, Utah
🔗 Register here: 2025-ut.cloudnativegeo.org 
How to strike a balance between open source and business is something I've been thinking about a lot. I shared my insights and how we might approach this with @tuistdev in my recent article:
open.substack.com/pub/thedevs... 
fun challenge! shortest I could golf it is
const findLongestStreak = (v, n) => Math.max(...v.map(x => ++x).join("").split(1).map(v => v.length >= n ? v.length : 0)) 
The Redis and pg URI options are documented here in our docs. We’d like to add a full docker compose example soon, but this should get you going.
www.inngest.com/docs/self-ho... 
We have released patches for a moderate security vulnerability for the vite dev server. Please update to the patched versions: 6.2.3, 6.1.2, 6.0.12, 5.4.15, 4.5.10
I launched a Substack to help developers gain insights into the tech industry from a capital perspective, fostering a healthier relationship with it. You can subscribe using this link:
thedevsdividend.substack.com/?r=2o4w2v&u... 
Great vibes!
I'm glad to hear that Alberto :)
🤖 Are you building apps with AI editors like Tabnine or Cursor?
💡 Check out our docs with tips & tricks for making the most out of AI tools when using Prisma!
www.prisma.io/docs/orm/mo... Vibe coding: Expectation vs Reality 
Shades of Purple. Let’s go!!!!
Yeah. That’s accurate. If you’re putting prod workloads on the self-host, I would run Redis and Postgres to back it instead of sqlite. You can also sign up for cloud for free to try things out pretty easily then move over to self -hosted later if you want.
Anything in particular that you’re curious about?
We should create a comparison table for reference, but our newest features like realtime and “connect” are also in self-hosted setup although may require some configuration. Self-hosting continues to get new benefits every week as that’s where our team commits our core code
It can be used in prod and devs are doing that today. It does not have feature parity with cloud though. It doesn’t have the o11y metrics dashboard, auth and bulk actions like replay or cancellation. All flow control and queueing are core to the self-hosted setup so execution is exactly the same!
raph levien blog post alert raphlinus.github.io/gpu/2025/03/...