Skill · forge · Administer a self-hosted Git forge
Monitor Forgejo through its logs and Prometheus metrics, fire an alert and diagnose a database outage
Read the logs of Forgejo and its database, have Prometheus scrape its /metrics endpoint with a token, fire an alert when Forgejo stops, understand why a stopped database does not bring up down and what /api/healthz reports, then diagnose two real database outages from the log.
Start lesson 1The forge domain
- 1 lesson
- ~50 min of reading
- 1 quiz
- 0 proof lab
The path
Where it comes from, where it leads
What you need to know first, where you stand on this skill, and what it opens next. Your status is computed in your browser, from what you have read and passed.
Before · 1 prerequisite
Recommended before · 2
This skill, for you
Monitor Forgejo through its logs and Prometheus metrics, fire an alert and diagnose a database outage
Computing
It unlocks · nothing yet
No other skill requires it: it is an end-of-path skill.
The path through the foundations From the most upstream foundation to this skill: what is in place, what remains to read.
Lessons
How to learn it
1 lesson, about ~50 min, in program order. Each lesson ends with its quiz.
The program
1 lesson · ~50 min
Beyond the lessons
Assess, practise, pass the proof
Reading a lesson confirms nothing. A skill is confirmed by a passed quiz, practised in a guided lab, and put to the test by a challenge or a mission; an imported lab result is not verified by the site.
Assess yourself
1 quiz
At the end of the lessons: passed at 70%, it confirms the skill.
Practice
No guided lab
No guided lab practices it yet.
Proof
No proof
Neither a challenge nor a mission with a proof yet.
Placement test
Preparing the questions…
Your answers in detail
For each question asked: your answer, the correct answer, its explanation and the page to reread.
Around it
Who requires it, who teaches it
Required by
Taught by
Same block · Administer a self-hosted Git forge
- Set up Forgejo on PostgreSQL behind a TLS proxy, reachable over HTTPS and SSH, then configure mail, LFS and sign-ups
- Govern access to Forgejo: organisations, teams and permissions, sign-in through an OIDC provider with an enforced second factor, and account support from the command line
- Secure a Forgejo instance: webhooks kept off the internal network, brute force banned with fail2ban, a break-glass administrator account, scoped tokens and signed commits
- Back up Forgejo, copy the encrypted backup off the machine, restore it on a blank stack and write the recovery runbook
- Maintain Forgejo and upgrade it: scheduled tasks, doctor and quotas, an upgrade rehearsed on a copy with validation criteria and rollback from the backup