Selfhosted

57412 readers

533 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Considering self hosting my own git repositories. What are some options? (lemmy.world)

submitted 1 day ago* (last edited 22 hours ago) by idunnololz@lemmy.world to c/selfhosted@lemmy.world

40 comments fedilink hide all child comments

Update

Forgejo seemed to be the winning answer so I tried setting it up. Total setup time was less than 10 minutes. I pushed 10 repositories to test it out and so far it seems pretty good. Thank you everyone for the answers!

As the title states, I am looking to host maybe ~100 git repositories locally on my home network.

I'm not planning on doing anything too crazy with my repositories. The solution doesn't need to support like 1000s of contributors however it should support the most basic features such as being able to see individual commits, branches, diffs, maybe some PR related mechanism, a web GUI, etc.

I don't like to tinker too much. The solution should work and be stable. Stability is a hard requirement. I want to write code and not have to worry about losing it. Yes I will make backups.

Please let me know what some of the best options are at the moment. Thank you!

you are viewing a single comment's thread
view the rest of the comments

[–] SpaceNoodle@lemmy.world 6 points 23 hours ago* (last edited 22 hours ago) (1 children)

Why forgejo instead of gitea?

[–] Creat@discuss.tchncs.de 16 points 22 hours ago* (last edited 22 hours ago) (1 children)

Forgejo was soft forked from Gitea after they went commercial and changed the license (I think). If there aren't any so far, expect pay walled features eventually.

Forgejo turned into a hard fork after communication issues between the teams. I haven't looked too deeply into it (as I don't really care about the fact that it's a hard fork now). This means while it used to be a drop-in replacement allowing you to go back and forth between the two, it's now an active conversion, I think.

[–] SpaceNoodle@lemmy.world 12 points 22 hours ago* (last edited 22 hours ago) (1 children)

Thanks for answering my question instead of only downvoting like half the other chuckleheads. Guess I'll migrate to Forgejo if my Gitea instance ever gets too old.

[–] moonpiedumplings@programming.dev 4 points 20 hours ago (1 children)

You should probably migrate now, forgejo is currently a soft fork that is fully compatible, but in the future they are planning to hard fork and not be compatible. Well, they are in the process of doing so right now.

[–] SpaceNoodle@lemmy.world 2 points 20 hours ago

Good to know, I'll look into it this weekend.