this post was submitted on 03 Aug 2024
62 points (95.6% liked)

Selfhosted

39962 readers
463 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

We are changing our system. We settled on git (but are open for alternatives) as long as we can selfhost it on our own machines.

Specs

Must have

  • hosted on promise
  • reliabile
  • unlikely to be discontinued in the next >5 years
  • for a group of at least 20 people

Plus

  • gui / windows integration
you are viewing a single comment's thread
view the rest of the comments
[–] swooosh@lemmy.world 3 points 3 months ago (2 children)

Is there a reason to choose gitlab over gitea?

We do not need ci/cd

[–] daco@lemm.ee 7 points 3 months ago* (last edited 3 months ago) (1 children)

If you don't need CI/CD I don't see any reasons to choose Gitlab over gitea. But I'm still testing gitea so take my words with a grain of salt :)

[–] Mubelotix@jlai.lu 6 points 3 months ago

Gitea also has excellent CI support with builtin compatibility with github

[–] lemmyvore@feddit.nl 2 points 3 months ago

If you don't need CI/CD I'm not sure why you need a centralized frontend at all. Git itself is distributed and you can setup any code flow you can think of. It has hooks that can be used to set up code quality checks on select branches. There are local history browser apps for every platform and IDE plugins.

A frontend is no substitute for developer communication — usually what the "PR" thing does is sugarcoat the fact the devs don't know how to use Git and/or don't talk to each other.