pjullrich

It does already, but it's not yet properly documented. You can already run your own Gitea runner and point it at Pushin. I'll also add managed CI runner support based on Firecracker VMs soon. Currently, I use self-hosted runners for my CI, but the UI is a bit rough. I wanted to merge a PR today that fixes all that but then HN happened so just bear with me a little longer :)

I think you should be able to do that if you run your own Tangled knot. I'd assume that you can host it under your domain which means your git service will remain even if Tangled itself is down or goes under.

Thank you! I hope the key shortcuts help too! I took that inspiration from npmx.dev :)

Even though we don't have a dog tax in Leiden, NL, where I live, Bella is certainly taxing being the 2yo Labrador pup that she is :D

- and I agree!

You can sign-up and I'll invite you to a chat room I'll set up based on chatto.run very soon. That'll be my main outlet for news and announcements.

You're free to use the API from your LLMs or other automations and push LLM-generated code, but not blast maintainers with your slop-machine.

That’s right. There are plenty of good options for OSS but few to none focused on both, public and private especially with team/enterprise support. That’s why I created Pushin :) simply to have a place to store both my public and private repos but still retain a community which you dont get on a self-hosted solution

Yes! I’d love to provide private or at least personal firehoses to users maybe based on the same lexicons as Tangled uses so that you can sync your Pushin repo to your own Tangled knot. That’d be cool, no? Also, sign-in with your atmosphere account, and generally offering lexicon-based API output to make it easy to sync to Tangled or somewhere else

Mostly her toys which I should throw without first taking them. Only throw, no taking

It's closer to walgit as it stores the packs in S3, but it uses Postgres for locking a repo during a push instead of using the Cursor/Walgit trick of using a WAL+CAS in S3. I've evaluated CAS on the Scaleway S3 service, but writing the WAL adds 240ms to every push, a cost we don't have with Postgres where it's a fast row lock. I also evaluated whether keeping a WAL would be useful, but ultimately decided against it because we can track everything the WAL tracks through the git history + audit logs without the write cost overhead.

Oh wow! I'll start pushin (pun intended) to get this ready in time for you to switch then :)

yes

Thank you and I absolutely agree! Pushin is merely one building block. We need a European-centric push in many products.

Yes.

Wenn du willst kann ich auch alles auf Deutsch schreiben aber dann versteht's keiner