Skip Navigation

Posts
10
Comments
1908
Joined
3 yr. ago

  • Maybe. The problems I have with codeberg are the lack of support to private repos and the 100 repo limit. I have some personal stuff in version control that I prefer to keep private, like notes, dotfiles, and shell history.

    At the same time, I'm not sure I want to maintain a self-hosted forge.

  • but the whole thing is self-hosted, not just the action runner, right?

  • Well, the opt-out argument really doesn't make any sense. The fact there's an opt-out tells me nothing about how deeply a feature is embedded, if anything, it tells me the exact opposite of what the article argues: the only reason we can disable it is because it's not deeply integrated. If it was, there most likely wouldn't be an opt-out.

  • not AI, and still not open source either

  • any alternatives to GH that allow private repos and self-hosted action runners?

  • ah right, my bad

  • fwiw, you can self host a GitHub actions runner

  • maybe they resumed development then, it was removed from Ubuntu and RHEL repos about 5 years ago when I had to look for an alternative

  • are you using a maintained alternative? Distros started to remove it from their repos years ago because it was not maintained anymore afaik

  • I'm the only user of my setup, but I configure docker compose stacks, use configs as bind mounts, and track everything in a git repo synchronized every now and then.

  • It doesn't require, but it runs better on GPU. It's not for nothing that modern terminal emulators like Kitty, Alacritty, Ghostty, and Wezterm ship with GPU support. Sure, they just "render text", but it is a rendering workload that is highly parallelizable. There's no reason to waste CPU cycles with that.

  • English, duh

  • need a hand? man touch

  • about the same specs as my TV, but 10" less and 4x its price

  • it's true, I was montana

  • it has always bothered me that checkout is overloaded: it can switch branches or discard pending changes in an unrecoverable way.

    so, PSA, you can replicate the safe part of checkout with git switch and the unsafe with git restore.

  • and now that the handover was confirmed, it's unlikely they'll do anything without hard evidence of malicious intent