371–380 of 425 posts
What are good alternatives to GitHub for private repos + actions? I'm considering moving my company off of it because of reliablity issues.
I've been using https://radicle.xyz/ + https://radicle-ci.liw.fi/ (in combination with my own ci adapter for nix flakes) for about half a year now for (almost) all my public and private repos and so far I really like it.
Is it really that much better than alternatives to justify these constant outages?
Earlier quoted context omitted.
Many teams work exclusively in GitHub (ticketing, boards, workflows, dev builds). People also have entire production build systems on GitHub. There's a lot more than git repo hosting.
It's especially painful for anyone who uses Github actions for CI/CD - maybe the release you just cut never actually got deployed to prod because their internal trigger didn't fire... you need to watch it like a hawk.
I'm grateful it arrived, but two and half hours feels less than ideal.
Earlier quoted context omitted.
I think this is being downvoted unfairly. I mean, sure, as a company accepting payment for services, being down for a few hours every few months is notably bad by modern standards. But the inward-looking point is correct: git itself is a distributed technology, and development using it is distributed and almost always latency-tolerant. To the extent that github's customers have processes that are dependent on service…
Being snapshot-based. Git has some issues being distributed in practice since the patch order matter which means you basically need to have some centralized authoritative server in most cases with more than 2 folks to resolve the order of patches for meaningful uses as the hash is used in so many contexts.
Earlier quoted context omitted.
Don't listen to the clueless suggesting Gitlab. It's forgejo (not gitea) or tangled, that's it.
Can you offer some explanation as to why Forgejo and Tangled over Gitlab or Gitea? I personally use Gitea, so I'd appreciate some additional information.
I'd had a gitea instance before and it was appealing insofar as having the ability to mirror from or to a public repo, it had docker container registry capability, it ties into oauth, etc; I'm sure gitlab has much/all of that too, but forgejo's tiny, tiny footprint was very appealing for my resource-constrained selfhosted environment.
Earlier quoted context omitted.
Because it's significantly harder to isolate problems and you'll end up in this loop * Deploy everything * It explodes * Rollback everything * Spend two weeks finding problem in one system and then fix it * Deploy everything * It explodes * Rollback everything * Spend two weeks finding a new problem that was created while you were fixing the last problem * Repeat ad nauseum Migrating iteratively gives you a foundatio…
So… create your shadow system piecewise? There is no reason to have "explode production" in your workflow, unless you are truly starved for resources.
Does it handle queries, trigger CI actions, run jobs?
We've migrated to Forgejo over the last couple of weeks. We position ourselves[0] as an alternative to the big cloud providers, so it seemed very silly that a critical piece of our own infrastructure could be taken out by a GitHub or Azure outage. It has been a pretty smooth process. Although we have done a couple of pieces of custom development: 1) We've created a Firecracker-based runner, which will run CI jobs in…
Github stability worse than ever. Windows 11 and Office stability worse than ever. Features that were useful for decades on computers with low resources are now "too hard" too implement.
Coincidence?