Zum Inhalt der Seite gehen

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 status.codeberg.eu/status/code… for more and up-to-date information.

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

Codeberg Service Status

This is an overview of the Codeberg Infrastructure.
status.codeberg.eu
#forgejo
Als Antwort auf Codeberg.org

Codeberg.org
Codeberg.org
• •
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.
Als Antwort auf Codeberg.org

Codeberg.org
Codeberg.org
• •
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.
Als Antwort auf Codeberg.org

mupan 📚
mupan 📚
• •

Thank you.

How is the fight against the proprietary wave going? Have you found a rather non-manual way to ensure compliance?

Als Antwort auf mupan 📚

Codeberg.org
Codeberg.org
• •
@mupan We'll publish a blog post on the introduction of quotas with Forgejo v9 soon (which can be manually increased on demand). It will reiterate our policy on private repositories. We don't have any plans to deal with such cases automatically at the moment - each situation is different. ~n
@mupan 📚
Als Antwort auf mupan 📚

Codeberg.org
Codeberg.org
• •

If they're not licensed, they're technically a subset of the category you're talking about. We have explained how we deal with such cases manually over the past few days as well. Is there anything specific that I can help with here? ~n

EDIT: social.anoxinon.de/@Codeberg/1…

Codeberg.org

2024-10-16 18:04:34


@girlintech I'm not responsible for handling these situations, but, from what I've gathered, it'd involve a warning, a popup with a reminder (if you use lots of space), or a personal ask to fix this (sent using your email address). Accidents happen and people can forget things sometimes.

This isn't a rule applying to all situations, however. But please don't panic. 😀 ~n

EDIT: A further clarification from ~f: social.anoxinon.de/@Codeberg/1…


Dieser Beitrag wurde bearbeitet. (1 Monat her)
Als Antwort auf Codeberg.org

Codeberg.org
Codeberg.org
• •

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.

Als Antwort auf Codeberg.org

Codeberg.org
Codeberg.org
• •

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

A hardware reboot of the existing machine is scheduled later.

Als Antwort auf Codeberg.org

Codeberg.org
Codeberg.org
• •

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

We are going down for maintenance now.

Als Antwort auf Codeberg.org

Codeberg.org
Codeberg.org
• •
Installation successful, rebooting ... it will, unfortunately, take a while until the service is fully restored.
Als Antwort auf Codeberg.org

Codeberg.org
Codeberg.org
• •
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.
Als Antwort auf Codeberg.org

Codeberg.org
Codeberg.org
• •

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

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.

An image from the front of a server, four hard drive bays are blinking. There are prominent stickers reading "Codeberg" and "forgejo".

Fukuoka, Japan

Contributors to Wikimedia projects (Wikimedia Foundation, Inc.)
Als Antwort auf Codeberg.org

Frank Kumro
Frank Kumro
• •
We need specs!!!
Als Antwort auf Frank Kumro

Codeberg.org
Codeberg.org
• •

@frigidcode See codeberg.org/Codeberg-Infrastr…

Not the latest stuff, but since we do not need the computing power and just the redundancy, the hardware does the job.


meta/hardware/aburayama.md at main

meta - Organizational repo for Codeberg's Infrastructure: Documentation, Organizing, Planning.
Codeberg.org
@Frank Kumro
Als Antwort auf Codeberg.org

Karoo
Karoo
• •
The R730 is a really great server, I loved working with them. I’m planning a home lab upgrade and I was eyeing with them.
Als Antwort auf Codeberg.org

IzzyOnDroid ✅
IzzyOnDroid ✅
• •
fingers crossed for an easy and painless update plus maintenance! 🤞
Als Antwort auf Codeberg.org

LWFlouisa
LWFlouisa
• •
Ive found it challenging to migrate pages over. I guess that must be the migration.

Diese Webseite verwendet Cookies. Durch die weitere Benutzung der Webseite stimmst du dieser Verwendung zu. https://inne.city/tos

⇧