What is the crowd's opinion of Gitea?

From 3.5 billion comments

It appears they are maintaining some repo's here but some are rather outdated. https://gitea.com/gitea

Edit: I found it odd that this Gitea instance is running the dev branch of Gitea rather than stable.

Thanks! Given the moderation "policies" and user attitude at r/linux, I guess this is a better place for the post. Please feel free to share the post, to reuse the arguments therein, and to send feedback to me on the Gentoo Forums or via email (see the contact info here). I do not attempt to persuade you to migrate to s6/s6-rc, but I strongly believe that the Linux circle will be in a much better condition when people actually understand the individual pros and cons of different init/rc systems.

The closest I am aware of is https://gitea.com/gitea/awesome-gitea#user-content-organizations

Generally we encourage self-hosting, so there isn't a huge drive for a public listing. Codeberg is the one I would probably point to first.

Or put a direct link to the latest version of the PDF on that first page? The only way I can see it is if I copy and paste "https://gitea.com/CasperVector/up2020/releases", or click on releases at the top, then download a zip or gzip file...

> a public instance we run ourselves at https://gitea.com/

Oh wow! I did not realize there was a first-party public instance of Gitea! This needs to be more visible and better publicized because I considered it one of the big things it was missing.

I'm migrating to a lot of open source, decentralized, and less corporate platforms/services/technology and so am thinking of leaving GitHub. I didn't know Gitea had a public first-party instance and am not ready to self host, so I was thinking I'd probably move to GitLab. This news changes things for me.

I do agree - to a point. Yet, when you have a chart that is bringing several services together, such as this one:

https://gitea.com/gitea/helm-chart/

Its not as clear-cut, as its deploying multiple services include Gitea, Memcache, database etc, bundling like this its "opinionated". One thing that does confuse me, is some charts want PVCs, other want the StorageClass.

As I mentioned, I am a hobbyist, and this is a something I need to get a better grasp of... PV and PVC's are easy to grasp, and they use a specified StorageClass - So I can understand a chart asking for a PV/PVC, but I can't see any reason in asking for a StorageClass 🤷‍♂️

Hi :)

• 16GB of RAM should be plenty since you're starting out. As you add more services you can reconsider buying more.
• Yep, OS and applications on the SSD and data on HDD.
• I haven't dipped my toes in proxmox yet, but maybe start with Ubuntu before adding more complexity.
• I like docker and docker-compose (I use it with portainer). Once you understand how it works, it allows you to quickly test services and your initial config is stored in a file.
• To complement the last point, I self-host Gitea, and I use it to store my compose files.
• If you have a domain, you can get LetsEncrypt certificates with certbot instead of self-signed certs.

It's linked to from this list of third-party packages, which in turn is footnoted in the Gitea installation docs. So yeah, not exactly easy to find.

Are you looking for a product to run or use? If you are running servers in house I would suggest you plan how you can effective test your application with the latest code before release. Do you need integration tests meaning do you have multiple apis or middleware services that need to be tested together? Do you have unit tests? You may be better off writing a script or test suite that devs can run locally and used with CI/CD. I've never used Gitea but this git repository has links to some CI/CD integrations you could use. https://gitea.com/gitea/awesome-gitea

I'd suggest to try and host gitea: https://gitea.com/

It is quite straightforward to host as it is a single binary and it doesn't have as many features as Gitlab or Github. There is a demo instance that you can use to see if it does what you need. One thing I particularly like is that you can set up repositories as mirrors, which might have made the youtube-dl debacle a bit less bad if it were widely used. Other than that there's no federation between instances afaik. You might want to look into <code>git-ssb</code> for that.

I found links in your comment that were not hyperlinked:

• Https://gitea.com

I did the honors for you.

^delete ^| ^information ^| ^<3

There's also https://gitea.com, which is going to be used by gitea for itself instead of GitHub like now.

It's hosted by a chinese company and I don't think they support Gitea except for hosting the "official" instance. Codeberg is definitely the better choice, starting from the fact they are a German non-profit that owns their servers and is in the EU.

>Gitea doesn't offer free hosting

wut
https://gitea.com (used by Gitea itself, but hosted by a chinese hosting provider)
https://codeberg.org (hosted by a german non-profit organization)

With the way things are devolving in terms of hosting reliability (i.e. getting automatically banned by big tech for vague reasons) and US laws that overstep their boundaries, I think the best way to make git repositories available to others is to host mirrors across as many services and networks as possible and switch your workflow (incl. issues) to a mail-based one. Here are a few non-US git hosting sites:

• https://gitea.com/ by the gitea project is hosted in China by a Chinese company.

• https://bitbucket.org/ by Atlassian is probably hosted in the US but is owned by a company headquartered in Australia.

Please feel free to nominate other git hosts that are open to the public.

On prem or cloud based?

Here is my experience for on-prem:

• GitHub Enterprise is the best out there. CS has always been up to par. Downside is that GHE is expensive ($250 a user, bought in 10 packs.) It also needs at least two nodes and either HCI or a good backend SAN/NAS for failover.

• Bitbucket is decent. It is an Atlassian product and does the job. However, it is Java based, and because of that, it is a porker, and backups can be an issue.

• GitLab's price is right. Even at its most expensive ($99/month/user), it still is less than half the price of GHE.

• I might recommend Gitea or GOGS as alternatives, for freeware options, as they are lightweight, but may not have the features you want.

For cloud:

AWS CodeCommit is used, but you will have to start from scratch when it comes to backups, as there isn't any real backup mechanism present.

Best thing to do is run some parallel tests. I recommend making sure your backup methodology works.

As for me, if I were standing up a DevOps shop, if I had Atlassian products already, I'd just bite the bullet and use Bitbucket, just for uniformity. GHE is nice, but IMHO... not worth the price. It is a nice limo ride, easy to update, and easy to backup and maintain, but it is just crazy expensive. GitLab isn't bad, and it would definitely in the running if there isn't an installed base of existing stuff.

Some details on [Gitea]() for those who are unfamiliar:

• Gitea is 100% open source.
• Gitea is funded on Open Collective
• It is a community-driven open-source project, not run or owned by a corporation
• It is designed for self-hosting and is much simpler and less resource-intensive than GitLab
• It has a first-party instance at Gitea.com if you're not ready to self-host. While it still has some of its own code hosted on Github, in the next release or two they should have migrated all of their code to be completely managed and hosted on Gitea.com.
• While it's not officially a promised feature, the community has indicated an interest in trying to move to a decentralized federated model, which would allow users of one Gitea instance to collaborate on projects and with users on another Gitea instance without making an account on that other instance.

For these reasons I consider Gitea to be the true FOSS alternative to Github and I think we should support it as much as we can.

We actually do have a flagship instance at https://gitea.com and as the post mentions, we are in the process of moving Gitea itself there.

We were hoping to have it moved before 1.10, however it may be between 1.10 and 1.11 due to some migration cleanup.

Also interesting thing I just learned (maybe everyone else already knew this) but Gitea has a public first-party instance at https://gitea.com/ if you're not interesting in self-hosting. They are apparently in the process of migrating the Gitea repo off of Github and onto Gitea.com.