I guess that's a no View quoted note →
GN image
$ ./gogs web 2026/01/14 22:56:50 [ WARN] Custom config "/home/git/Downloads/gogs/custom/conf/app.ini" not found. Ignore this warning if you're running for the first time 2026/01/14 22:56:50 [TRACE] Log mode: Console (Trace) 2026/01/14 22:56:50 [ INFO] Gogs 0.14.0+dev 2026/01/14 22:56:50 [TRACE] Work directory: /home/git/Downloads/gogs 2026/01/14 22:56:50 [TRACE] Custom path: /home/git/Downloads/gogs/custom 2026/01/14 22:56:50 [TRACE] Custom config: /home/git/Downloads/gogs/custom/conf/app.ini 2026/01/14 22:56:50 [TRACE] Log path: /home/git/Downloads/gogs/log 2026/01/14 22:56:50 [TRACE] Build time: 2026/01/14 22:56:50 [TRACE] Build commit: 2026/01/14 22:56:50 [ INFO] Run mode: Development 2026/01/14 22:56:51 [ INFO] Available on http://localhost:3000/ View quoted note →
#gogs installed successfully!
let's try #gogs
From source - Gogs
Gogs is a painless self-hosted Git service.
Totally giving up on installing #forgejo on 32bit (linux-x86) checkmate, the building of nodejs failed (build-essential too old)
Trying to use old hardware as a 'learning method' is very underestimated when working in IT
#forgejo installation seems like an overkill I am forced to build nodejs from source because since version v9 nodejs package for x86 linux is not provided
Index of /dist/latest-v9.x/
 maybe I should install #gogs instead
GitHub
Gogs
A painless self-hosted Git service. Gogs has 17 repositories available. Follow their code on GitHub.
I think what went wrong in my #forgejo installation was the binaries did not match the environemnt setup