this post was submitted on 20 Aug 2024
160 points (90.4% liked)

Selfhosted

39435 readers
3 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
 

I've recently set up my own Gitea instance and I figured I'd share a simple guide on how to do it yourself. Hopefully this will be helpful to anyone looking to get started.

If you have any feedback please feel free to comment it bellow.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 147 points 2 months ago* (last edited 2 months ago) (3 children)

I'll be that guy: Use forgejo instead, its main contributor is a Non-Profit compared to Gitea's For-Profit owners

[–] [email protected] 19 points 2 months ago (3 children)

Silly question but what is the problem with gitea being for profit?

[–] [email protected] 65 points 2 months ago

I guess out of fear that we get another gitlab situation, where the open source offering has a load of key features eventually kept behind a paywall

[–] [email protected] 37 points 2 months ago

At some point they will do a Redis or Terraform and say no more open source, pay us to use it.

All contributions are now owned by us and not by the person who wrote it.

[–] [email protected] 19 points 2 months ago

As the other commenter already said it's an abundance of caution. GItea is already moving in the direction of SaaS and an easily self-hostable solution runs counter to that plan (Gitea is already offering a managed Cloud so this is not a hypothetical). One thing that has already happened is Gitea introducing a Contributor License Agreement, effectively allowing them to change the license of the code at any time.

[–] [email protected] 9 points 2 months ago* (last edited 2 months ago) (2 children)

Thanks, I always keep forgetting what this ones called. I use a build of gitea from before it became shit but I keep telling myself I need to change to "that better one".

[–] [email protected] 3 points 2 months ago (1 children)

If it helps, it's supposed to be a drop-in replacement.

[–] [email protected] 1 points 2 months ago

It's a hard fork by now, but the switch should still be pretty painless.

[–] [email protected] 2 points 2 months ago

Same. It’s been on my list for too long.

[–] [email protected] 5 points 2 months ago (1 children)

Well I learned something new today.. maybe its time to plan a migration

[–] [email protected] 8 points 2 months ago (1 children)

I think for now Forgejo is a drop-in replacement. However since they are a hard-fork, at some point in the future they will diverge enough to be mutually incompatible, so the clock is ticking on migrating.

[–] [email protected] 4 points 2 months ago

From what I have read on the FAQ they already did a hard fork from Gitea version 1.21.11 on, which was earlier this year

https://forgejo.org/faq/#im-sold-are-migrations-from-gitea-to-forgejo-possible