3 ms·

Makes sense. SourceHut is probably perfect for Postmarket OS. Both have a strong taste for minimalism and free software. Choosing hosting provided by SourceHut

by jraph 4y ago

Makes sense. SourceHut is probably perfect for Postmarket OS. Both have a strong taste for minimalism and free software. Choosing hosting provided by SourceHut instead of self hosting may also help fund SourceHut itself so that's good too. Go for it! I too am not really happy with GitLab.com. It requires contributors to fill a reCAPTCHA and I'm not a fan of it being open core. I chose Gitorious (and was moved to GitLab.com when it disappears) precisely because I don't want to endorse proprietary software, nor tracking. I don't want to run proprietary code - from Google! - and, above all, make people run Google's proprietary code and tracking. That's just not coherent. GitLab is considering moving to hCaptcha if I remember correctly but that's still proprietary and still a third party. So I made the jump two weeks ago. I now self host my code. I pay for the resources I use so no more strange free lunch. I personally find SourceHut a bit bare but that might just be habits. I picked Gitea instead. People can log in with their GitHub or GitLab account if they wish so the argument that it prevents contributions because you have to create yet another account does not hold. Gitea is quite fast and works well without JS at least for consulting the code. It's quite easy to set up - I have already been self-hosting a number of services for years know. It's also very straightforward easy to use - much more than GitLab so far. I don't force anybody to run proprietary software to use or contribute to my projects. For people who don't want to self host but would like an alternative to GitLab, Codeberg [1] is worth checking out, in addition to Source Hut. It uses Gitea. It's been mentioned in one of the latest blog posts from Drew Devault (the creator of SourceHut) by the way. It's hosted in Germany, too, if it matters. I guess it would be good to support them. [1] https://codeberg.org/ https://codeberg.org/

KronisLV 4y ago
> So I made the jump two weeks ago. I now self host my code. I pay for the resources I use so no more strange free lunch. I also chose this exact approach. Previously, I ran GitLab, GitLab Registry and GitLab CI and while I think that it's a nice ecosystem to work within (especially at work, where it still is an excellent option, as long as someone else manages the instance), it was also a bit heavy on the resources and updating across major releases... just didn't work. I wrote about that previously, "GitLab updates are broken": https://blog.kronis.dev/everything%20is%20broken/gitlab-updates-are-broken https://blog.kronis.dev/everything%20is%20broken/gitlab-upda... So, eventually I switched over to Gitea, Drone CI and Nexus, all of which now comfortably live on a single VPS with 4 GB of RAM. The performance is good, the resource usage is acceptable and when things break it just takes the individual component down instead of the whole platform (which is also nice for more granular updates). I actually did a writeup about the switch in more detail "Goodbye GitLab; Hello Gitea, Nexus and Drone": https://blog.kronis.dev/articles/goodbye-gitlab-hello-gitea-nexus-and-drone https://blog.kronis.dev/articles/goodbye-gitlab-hello-gitea-... Of course, actually applying those updates is still somewhat of a problem and will definitely be so until the end of time or until I get enough spare income to make someone else worry about all of that for me (including moving back to cloud platforms and paying for private Docker image storage, CI etc.). But honestly my current setup is good enough for me, at about 6 euros per month for the hosting (my time is more or less worthless so not counting that).
joshxyz 4y ago
wow gitlab must be truly evil for being proprietary
- jraph 4y ago
  When I write GitLab.com, I'm referring to the service, not the software project. The service relies on reCAPTCHA. The project provides the feature but does not require it nor enable it by default. I'm not going to say that GitLab is evil. I don't think it is. I don't see the world like this anyway. But yes, there are proprietary bits involved in Gitlab.com (and the service actually runs Gitlab EE afaik). What do you expect from me as a free software enthusiast? Close my eyes and suck it, or live to my principles, which is easy considering there are good open source forges that are also not based on an open core model? As cool as GitLab is to the eyes of many people, I don't like making unnecessary exceptions. Now, I would still be fine self-hosting GitLab CE. But from a technical perspective, Gitea is probably better than GitLab for me: it's lighter on resources and easier to maintain. I also like the UI better.
  - joshxyz 4y ago
    on features that are useful for individual users but are only available enterprise-only, kinda makes sense. https://sso.tax/ https://sso.tax/ for example lol

by jraph 4y ago

KronisLV 4y ago

> So I made the jump two weeks ago. I now self host my code. I pay for the resources I use so no more strange free lunch. I also chose this exact approach. Previously, I ran GitLab, GitLab Registry and GitLab CI and while I think that it's a nice ecosystem to work within (especially at work, where it still is an excellent option, as long as someone else manages the instance), it was also a bit heavy on the resources and updating across major releases... just didn't work. I wrote about that previously, "GitLab updates are broken": https://blog.kronis.dev/everything%20is%20broken/gitlab-updates-are-broken https://blog.kronis.dev/everything%20is%20broken/gitlab-upda... So, eventually I switched over to Gitea, Drone CI and Nexus, all of which now comfortably live on a single VPS with 4 GB of RAM. The performance is good, the resource usage is acceptable and when things break it just takes the individual component down instead of the whole platform (which is also nice for more granular updates). I actually did a writeup about the switch in more detail "Goodbye GitLab; Hello Gitea, Nexus and Drone": https://blog.kronis.dev/articles/goodbye-gitlab-hello-gitea-nexus-and-drone https://blog.kronis.dev/articles/goodbye-gitlab-hello-gitea-... Of course, actually applying those updates is still somewhat of a problem and will definitely be so until the end of time or until I get enough spare income to make someone else worry about all of that for me (including moving back to cloud platforms and paying for private Docker image storage, CI etc.). But honestly my current setup is good enough for me, at about 6 euros per month for the hosting (my time is more or less worthless so not counting that).

joshxyz 4y ago

wow gitlab must be truly evil for being proprietary

jraph 4y ago
When I write GitLab.com, I'm referring to the service, not the software project. The service relies on reCAPTCHA. The project provides the feature but does not require it nor enable it by default. I'm not going to say that GitLab is evil. I don't think it is. I don't see the world like this anyway. But yes, there are proprietary bits involved in Gitlab.com (and the service actually runs Gitlab EE afaik). What do you expect from me as a free software enthusiast? Close my eyes and suck it, or live to my principles, which is easy considering there are good open source forges that are also not based on an open core model? As cool as GitLab is to the eyes of many people, I don't like making unnecessary exceptions. Now, I would still be fine self-hosting GitLab CE. But from a technical perspective, Gitea is probably better than GitLab for me: it's lighter on resources and easier to maintain. I also like the UI better.
- joshxyz 4y ago
  on features that are useful for individual users but are only available enterprise-only, kinda makes sense. https://sso.tax/ https://sso.tax/ for example lol