Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
I imagine most people here already know this, but - you don't really need anything but git installed on the server. you can create a repo, push to it, pull off it, branch, merge, do whatever you can with the cli, all that web GUI is just optional. integrates just fine with vscode and clones.
so if you don't need a web UI, a truly lightweight solution is already preinstalled.
all that web GUI is just optional
Yet git includes one.
But tbf to OP, CI/CD is a different matter.
Even though you’d prefer do everything in cli which is arguable alternative , what about cicd part? Teams need that one
Ok, but "lightweight" with those hardware requirements?
Ok, what requirements you think is lightweight ? We talk about team work anyway , where concurrent builds run …
Ah, so it's for the case that multiple builds run? But what is the minimum requirements if no builds run, the server only?
I mean if it happens when two different repos would run builds simultaneously. Usually average team may have few repos . If there is no builds at all , I think it’s even less by RAM - as all the dependencies are pretty much in binary complied form - so , say 2 GB would be enough . As backend is pure go ( echo framework ) and is extremely low footprint and as for the CI runner is just a dispatcher background process gets run by very efficient rakupp and just idling . All the git operations are also very lightweight - native smart http / CGI protocol is in use under the hood if you need details
