DumbMonit
IntegraçõesAplicações auto-alojadas
Monitorizar Forgejo / Gitea com o DumbMonit
Health check, repository, user and organisation counts, scheduled tasks running on time, Actions runners online or not.
DocumentaçãoSite oficial: Forgejo
As descrições estão em inglês, como no produto. Os rótulos da página seguem o seu idioma.
O que o DumbMonit vigia
Forgejo and Gitea share the same REST API, so DumbMonit reads both with one collector: whether the instance answers, its health check, how many repositories, accounts and organisations it holds, whether its scheduled tasks (repository checks, cleanups, the update checker) still run on their own interval, and whether its Actions runners are online.
Utilização típica. Forge: health check, scheduled tasks, Actions runners, repository/account counts
Exemplos
- Forgejo
- Gitea
Como se liga
O que precisa
- Access tokenA site administrator's access token, sent as "Authorization: token …". A token without admin rights still works, but only the version and the account's own repositories are read.
Portas de rede a abrir
3000/TCPAPI (HTTP, default)443/TCPOnly with the https scheme behind a reverse proxy
Passos de configuração: Create an access token in Forgejo or Gitea
On a site administrator account, open avatar → Settings → Applications → Generate New Token.
Name it as follows and tick only the scopes listed below.
dumbmonitGenerate the token and copy it: Forgejo shows it only once.
In DumbMonit, enter the server's address and paste the token.
Atenção. Forgejo and Gitea have no read-only administrator role, so the token can do whatever its account can: use a dedicated bot account, not your own.