running all my homelab / private repos off of a tiny gitolite3 server, and i'm always amazed that it all runs on an alpine linux VM that uses 75mb of RAM.
for anything even just sharing with friends or whatnot i won't recommend it though, people do love their web-UI and having to explicitly give someone access can turn off people already.
You might need to use another user if you want to set its shell to `gitolite-shell username` (no command= for password authentication) but then you'd need to chain sudo or something to have Gitolite run under its own user again... Seems very tricky.
Or maybe you can write a shell that runs a gitolite-shell command is its arguments are not already gitolite-shell?
Ooh this is very nice. Might use this for private projects.
Problem with this is that it’s likely very unfamiliar with most folks. At least with gitea or gl-ce, there’s a familiar interface 99% of developers can use to browse and search code.
Like if I want to share a quick nixOS config, I doubt most people would even be willing to pull the code and only browse via web interface.
I am of the school of thought that you should be using multiple remotes anyways. I don't think there is a good reason not to. Codeburg and, as another mentioned, Sourcehut may be good places to host your code in addition to your self hosted remote.
> Also gitea is a much more lightweight option and can use sqlite for db. Much easier to deploy on a rpi
Worth mentioning Forgejo as well (https://forgejo.org), which is Codeberg's fork of Gitea. Same features and as lightweight as Gitea. Hard-forked a couple of months ago after some transparency concerns from the new parent company that owns Gitea now.
Because functionality isn’t the only thing everyone cares about, I use Forgejo for ideological reasons and so do probably most people since it’s mainly an ideological fork.
Why would it not be worth mentioning? The question is quite strange.
The project and community might be worthwhile, but as long as the product is the exact same, I don't see what there is to mention. I'm excited to see what the future holds though, more attention in this space sure sounds good.
If you're concerned, you should switch the license of your code, not really where you host it. As long as your license allows LLM/AI models to train on your code, why would you be mad that it does?
Training on your code and using your code are very different things. As a human, if your code is open, I can read it, learn how it works and reuse my knowledge to create proprietary source code without infringing on your license.
Attribution doesn’t apply on training. We’d all be screwed otherwise, it would mean you’d have to attribute everything you learned while reading open source codes to every codebase you read every time you write code.
As I said: it would mean you’d have to attribute everything you learned while reading open source codes to every codebase you read every time you write code.
You don't have to run a Pi from an SD card nowadays, and shouldn't do if you can help it. They've supported USB boot for a while and the Pi5 can also boot from an NVMe SSD hooked up to the exposed PCIe lane.
As others have said, Pi now supports USB boot. An inexpensive USB to sata adaptor and a 128GB SSD (~$15) is the most inexpensive option to get started and performs very well.
This happened to me Tuesday September 28th 2001 at 3:30pm. I know because I never rewrote the complicated e-paper code that I lost when my SD card died without a backup :(
Side note: Gitlab is one of the few companies to provide a self hosted version of their VCS.
https://docs.gitlab.com/ee/install/requirements.html
Also gitea is a much more lightweight option and can use sqlite for db. Much easier to deploy on a rpi