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

Your registration to Codeberg e.V. is appreciated to bump the members count from 599 to 600.

Join #Codeberg today and sustain the development of our platform as well as #Forgejo as a base.

https://join.codeberg.org/

It seems like our joint stand with @forgejo at #FOSDEM2025 has been accepted, thank you @fosdem!

For those of you that don't know, #FOSDEM is an annual conference for free and open source software taking place in Brussels. We'll be there throughout the event to exchange words and/or stickers with some of you.

See you in February!

https://fosdem.org/2025/news/2024-11-16-stands-announced/

We are looking for #hardwareDonations:

If anyone has old servers, drives and equipment and shipping to/in Germany is not a problem, we appreciate your offers.

If you work for a company, we could eventually figure out donation receipts, too.

(Target location is Berlin, pickup in vicinity is not a problem)

Specifically, we could currently make use of SFF-8643 or SFF-8087 cables, if you have some spare 😉

#server #hardware

Codeberg is going down for maintenance in about 15-30 minutes, hopefully lasting no more than 30 minutee. Please schedule accordingly and take a break :)
Apologies for the inconvenience.

Do you want to improve #codeberg and have nothing to do for the weekend yet? Check out the #GoodFirstIssue­­ s at Forgejo and let friendly maintainers help you if necessary: https://codeberg.org/forgejo/forgejo/issues?labels=222666

Dear #GitHub users, if you prefer the orange-themed heatmap for #halloween and would like to see it all year long: feel invited to move to #Forgejo or #Codeberg (and choosing a forgejo theme in the appearance settings). It's the default colour here.

We're now installing new network hardware, requiring to take down the machine.

We are going down for maintenance now.

Installation successful, rebooting ... it will, unfortunately, take a while until the service is fully restored.

The maintenance was successfully completed and Codeberg is back in service. Additionally, we now have a 10G fiber interconnect to our next server, an important step towards our new setup.

👋 Say hi to "Aburayama", our second server named after the mountain that inspired the first (now retired) Codeberg logo: https://en.wikipedia.org/wiki/Mount_Abura

Just in case people want to know what's running inside it, we placed some stickers prominently on front.

Thanks to everyone involved for their work, and for your patience during the setup.

Codeberg has two downtimes scheduled in the next two days, upgrading #Forgejo to the latest version as well as operation on our owned hardware.

See the notification at https://status.codeberg.eu/status/codeberg for more and up-to-date information.

Thank you for your understanding. We'll try to minimize service disruption.

Sun 2024-10-20, starting around 16.00 UTC / 18.00 CEST: We're preparing for and updating Forgejo to version 9 which will probably involve a brief period of downtime in best case.

Mon 2024-10-21, starting around 18.00 UTC / 20.00 CEST: We are shipping a new system to the datacenter, proceeding with our infrastructure expansion and redundancy plans. This requires the installation of a new network card into existing hardware and a reboot following the operation. Service to Codeberg.org will be interrupted for up to 30 minutes. If all goes well, this will allow us to transition services to the new setup gracefully, avoiding downtime due to hardware reboots.

Reminder: We're soon on our way to the datacenter, starting maintenance in about two hours, which involves about 30 minutes of downtime for Codeberg.

We know that our availability was limited recently due to various factors, and we're sorry to add on it today, but it's the way to make the future setup more reliable.

We'll keep you updated as time permits.

*click* - a new server was just installed physically. Now cabling and testing begins.

A hardware reboot of the existing machine is scheduled later.

In the meantime, you could join our Matrix space and our Matrix room (#codeberg-space:matrix.org and #Codeberg.org:matrix.org respectively) again for real-time discussions with others in the same boat.

Completely optional, of course. ~n

Hi. Yes, we have a full outage right now (status.codeberg.eu).

This acknowledgment comes from the social media manager that _isn't_ a system administrator. I can't share more details right now, so all I have to say is the following for now: It has been a weird and challenging week, sorry for the inconvenience. ~n

@civodul @ieure Hi! If you ever planning to move away, keep in mind that we have a guide on using Codeberg as an SSO provider using Keycloak (https://docs.codeberg.org/integrations/keycloak/) so as to reduce friction during the transition process. You may need to reach out to us for mutual coordination if the migration process goes wrong for some reason (which could happen, given the large size of your project). ~n

For those still wondering about why they were "not allowed" to scan the other QR code: I suspect this is related to potential abuse vectors via QR codes (yes, we know, requiring the hacker to spoof it via a fake app instead of an ebook is not the answer).

Watch https://www.youtube.com/watch?v=cIcbAMO6sxo or read https://www.revk.uk/2020/01/eicar-test-qr.html for some background.

~f

@lynn We managed to break two of these server power supplies with a firmware update. And while searching for a fix, we have found videos demonstrating these very PSUs taking fire.

So ... you never know! ~f