gogs
The painless way to host your own Git service
Runssource: GitHubhomepageGoMITcommit aec2b842cdb6
Go, MIT licensed. The project labels itself: docker, git, go, gogs, mysql, postgresql, raspberry pi and self hosted.
gogs runs. An Argusic agent installed it in 27 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Gogs 0.15.0+dev builds, all Go tests pass, and the web server launches on http://localhost:3000 serving the React frontend correctly (200 OK, title 'Gogs').
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 90 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.
- Dev mode server failed with 502 due to missing Vite proxy on port 51735 minutes
- Go compiler not installed3 minutes
- Node.js v18 too old for pnpm@112 minutes
- ssh-keygen not found (openssh-client not installed)2 minutes
- RUN_USER mismatch prevented server start (default 'git', actual 'runner')2 minutes
- moonrepo CLI not installed1 minute
- Install time
- 27 minutes
- Cold machine to finish
- 31 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- Model tokens used
- 100,458
- Exact commit tested
- aec2b842cdb6
- 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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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.
LEVEL = info
EOF
echo \"Config updated - removed deprecated options\"" in /work/repo
succeeded in 0ms:
Config updated - removed deprecated options
Now let me compute the final times and produce the result.
exec
/bin/sh -lc "cat /proc/uptime 2>/dev/null | awk '{printf \"uptime seconds: %d\\n\", int("'$1)}'"'" …
succeeded in 0ms:
uptime seconds: 3320588
tokens used
100,458Replay 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.
- Recovered from all 6 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 did not, or is not known
- Took 27 minutes to install, slower than the median of the 8 comparable projects Argusic has measured.
Of the 9 docker projects Argusic has installed and timed, gogs was the 8th fastest to reach a running state, and 8 of 9 reached one at all.
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)
dockergitgogogsmysqlpostgresqlraspberry-piself-hostedsource-code-managementsqlite3version-control
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/gogs)Questions
- Does gogs run?
- Yes. gogs runs. Argusic installed and launched it on a clean machine in 27 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test gogs?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit aec2b842cdb6. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test gogs?
- The run that produced this verdict cost $0.16: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does gogs take to install?
- 27 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 gogs need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing gogs?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does gogs compare with the alternatives?
- Of the 9 docker projects Argusic has installed and timed, gogs was the 8th fastest to reach a running state, and 8 of 9 reached one at all.
- Where is the evidence for gogs?
- 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.