Moving our server away from Codeberg

Lab News (announcements)
1

Everything has moved to Butterforge (and nothing breaks)

The JustAGuy Linux projects have a new canonical home: Butterforge, my
self-hosted forge at https://justaguy.dev ā€” repos, issues, wikis, releases,
all of it. This includes ButterRepo, cosmic-trixie, the WM setups,
butterscripts, and the Butterbian ISOsā€™ source.

If you use ButterRepo or cosmic-trixie: you donā€™t have to do anything

The old justaguylinux.codeberg.page addresses are now automatically
synced mirrors ā€” every package update lands there too, and theyā€™re staying
up indefinitely. Your system keeps updating like nothing happened.

When you feel like switching to the canonical address (same packages, same
signing key, only the URL changes):

sudo sed -i 's|https://justaguylinux.codeberg.page/butterrepo|https://apt.justaguy.dev|' /etc/apt/sources.list.d/butterrepo.list
sudo apt update

Prefer reading before running? Thereā€™s a short migrate.sh in the repo that
does exactly this with a backup. And the laziest path: install
butterrepo-keyring (now in the repo) and future upgrades handle the switch
automatically. cosmic-trixie users: same story, see its README.

Why (and no, not the vote)

Given the timing, let me be direct: this move has nothing to do with
Codebergā€™s recent policy vote. Iā€™d been planning it before, and I didnā€™t
really ā€œleaveā€ at all ā€” Iā€™m staying a contributing member of Codeberg,
they still host our mirrors, and their accounts are still how you sign in
to file issues on my forge. I moved my hosting, not my support for the
project or for FOSS.

The real reason is simpler: reliability. Slowdowns and down status had
become routine, and that stopped being an inconvenience the day your apt
updates and fresh installs started depending on my URLs answering. Every
Butterbian and butterknife ISO out there phones home to these repos at
first boot ā€” a down host doesnā€™t just slow your upgrade, it breaks a brand
new install. I can tolerate a slow page; I canā€™t ask you to tolerate a
failed apt update or an ISO that boots but canā€™t finish setting up.

I say that with sympathy, not blame ā€” Codeberg is a donation-funded
nonprofit absorbing an era of explosive growth, and my projects (an 8 GB
package repo, apt hosting, ISOs) were exactly the kind of weight making
that harder. Moving to my own hardware fixes my usersā€™ problem and takes
my load off their shoulders in the same motion. If youā€™re a Codeberg fan:
stay one. Our mirrors still live there, and so does our login button.

Beyond that, owning the stack end to end is consistent with how this
project thinks about privacy:

  • The apt endpoints keep no access logs, by policy ā€” and the exact web
    server configuration is published in the repo (docs/apt-vhost.Caddyfile)
    so you can verify what runs.
  • No CDN, no third party between you and the packages.
  • Issues and bug reports now happen on the forge ā€” sign in with your
    Codeberg account     and youā€™re set, no new account needed.

The links that matter

Old Codeberg links keep working via the mirrors. Questions welcome below.

1 Like