Notices by Codeberg.org (codeberg@social.anoxinon.de), page 3

united against github

👤: Drew DeVault, @n0toose
📷: @taavi

@andre_601 @forgejo We already have a squirrel on https://forgejo.org, but unfortunately, we asked a suiter to show up and help us promote Forgejo but he was not available. ~n

fosdem besties

👤: @nick_vh @n0toose
📷: @Gusted

@badnetmask At Codeberg, we have set the ghcr.io/catthehacker/ubuntu:act-22.04 image by default, which has quite some tools built-in (not sure if it covers your needs).

"Off-the-shelf governance models for small FOSS projects?" by @pintoch (2024-12-20)

https://antonin.delpeuch.eu/posts/off-the-shelf-governance-models-for-small-foss-projects/

We read that interesting blog post about governance in open-source recently. We chose to share it here because it is worth a read, particularly the section "The default governance model that forges push us into". ~n

Hi everyone, we apologize for the current downtime. Our host refuses to detect one of the RAID boot drives and doesn't boot up properly. We are still investigating.

Since we recently extended our setup, we could in worst case restore on one of the other hosts. However, the database is not clustered yet, so we'll first try to bring up the primary instance.

Hey everyone, we apologize for the current unexpected downtime.

We have had a long-standing issue where certain data could not be stored properly. For example, Git allows users to have both a main and a MAIN branch (different casing), but Codeberg could not store it, because our database was case-insensitive.

We have been preparing and testing a fix (which is currently converting the database tables). However, we missed that certain operations would fail during the migration.

…

… To prevent any damage and inconsistencies because of failing queries, we have temporarily disabled access to Codeberg.org while the conversion is running.

We don't have a good estimate about how long this will take, but the largest tables are converted and we expect the operation to complete within some minutes.

We apologize for the oversight and the interruption to your workflows. Thank you for your patience and support.

We are back online. I hope you all enjoyed the break.

We are upgrading Forgejo to version 10 later tonight, starting around 20.00 UTC / 21.00 CET.

Necessary database migrations will require a short downtime of about five minutes.

Please prepare for an interruption of your work. We apologize for the inconvenience.

Help from #podman or #docker users welcome!

We have started to offer open alpha access to a hosted Forgejo Actions CI runner. Unfortunately, there are many jobs that can crash the runner for every user reliably, and many users execute them inadvertently.

To save cost and disk wear, we want to keep temporary writes inside the CI builds in RAM and only store the images persistently.

However, the setup is apparently incorrect and we need help figuring it out.

See https://codeberg.org/actions/meta/issues/11

@jwildeboer
@bookwar
We'll definitely be at FOSDEM again, and it was a pleasure to talk to some of you last year. Maybe we can schedule a meetup in one of the evenings, talking in depths about Forgejo and collaboration opportunities.

We can also schedule an online meeting before or after.

Let us know. ~f

An exciting evening ahead of us: We are performing maintenance on our #Ceph storage system and will distribute data across the machines for the first time.

We expect no or little interruption of our services, but performance might degrade while the new nodes are backfilling.

If you receive in-app notifications which lead to 404 pages or threads that don't contain new messages, it is also likely that they have been cleaned up.

Unfortunately, it is currently very difficult to also remove the notifications when deleting spam users.

We apologize for the inconvenience.

Hint: If "security researchers" or "computer experts" link to an http-only website, you can almost always consider it a scam.

🔔 Heads-up: There is currently a #phishing campaign targeting #Codeberg users.

If you receive a notification that insults you and your project for poor code quality, combined with an offer to "fix" the problems when you send some money, please ignore and report to us: Mention "@moderation" in response to the issue or forward the email to abuse@codeberg.org.

We are trying to stay ahead of the noise before the notifications are sent.

Nonprofit work is hard. It takes a lot of time, dedication and, more often than not, you see volunteers taking in multiple different tasks and responsibilities to keep everything running. Thankfully, we occasionally get external contributors that help us out!

For instance, I would post something serious so as to promote our nonprofit, but it seems like #GitHub decided to help us with the marketing for the day by sending a bunch of its users (multiple) emails about GitHub Copilot. 😅

This is intended to be a lighthearted post, but if you're interested in helping us, as well as other self-hosters and public instances, you may be interested in Forgejo's issue tracker.

(We are also happy to help you find something else. :D)

https://codeberg.org/forgejo/forgejo/issues

@jwildeboer
TOKEN_ENV vs CBTOKEN_ENV mismatch? Your history looks frustrating, though. I don't know when Woodpecker 3.0 will be deployed, but it should continue working until then.
@m2vh

@jwildeboer
Have you tried `from_secret` instead of `from-secret`? Might do the trick (not tried, though).

BTW, Codeberg also offers hosted Forgejo Actions as of recently, and feedback is very welcome: https://codeberg.org/actions/meta/
@m2vh