gitea
Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
Runssource: GitHubhomepageGoMITcommit 231ee19cff64
Go, MIT licensed. The project labels itself: bitbucket, cicd, devops, docker registry v2, git, git gui, git lfs and git server.
gitea runs. An Argusic agent installed it in 13.2 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Gitea builds from source with Go 1.27.1 and Node 22.18.0; all 637 backend unit tests pass (0 failures); the web server starts and serves HTML on port 3000, returning HTTP 200 with a valid page including CSP headers and Gitea UI markup.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js v18 too old (needs >=22.18.0)1.5 minutes
- Go 1.27 not found on system1 minute
- pnpm not installed; npm install -g pnpm failed with EACCES1 minute
- Test TestGitDiffTreeRespectsDiffOrderFile/GlobalDiffOrderFile failed: git config set --global syntax requires Git >=2.45 (system has 2.43)1 minute
- rolldown native binding missing after Node upgrade0.5 minutes
- Install time
- 13 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- make test-backend: 0 FAIL (all tests passed); curl -sS http://localhost:3000/ returned 200 and valid Gitea HTML
- Model tokens used
- 131,025
- Exact commit tested
- 231ee19cff64
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
/bin/sh -lc 'date +%s' in /work/repo succeeded in 0ms: 1789370985 exec /bin/sh -lc 'echo "Started at 07:16:40" && echo "End at $(date +%H:%M:%S)"' in /work/repo succeeded in 0ms: Started at 07:16:40 End at 07:29:52 All passing. Here's the summary: tokens used 131,025 All passing. Here's the summary:
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 13.2 minutes.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
bitbucketcicddevopsdocker-registry-v2gitgit-guigit-lfsgit-servergiteagithubgithub-actionsgitlabgogolanghacktoberfestmaven-servernpm-registryself-hostedtypescriptvue
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/gitea)Questions
- Does gitea run?
- Yes. gitea runs. Argusic installed and launched it on a clean machine in 13 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test gitea?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 231ee19cff64. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test gitea?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does gitea take to install?
- 13.2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does gitea need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing gitea?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for gitea?
- All 3 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.