@nobodyinperson@fosstodon.orgOh man... #Gitea forces *everyone* in an organisation (i.e. group) to auto-watch every single repo in the org - you have to *manually* un-watch every single repo you're not interested in.
This causes Issues to be very unusable, as *everyone* is notified of *every single issue* activity.
Who invented this? 😩
@tenderlove@mastodon.socialI set up Gitea on my local file server and it was really easy (though it tries to talk you in to setting up mysql but I insisted on using sqlite). It works really well! I didn't think I'd use a self hosted git server, but it turns out I'm using it a lot. Definitely recommend https://about.gitea.com<…
@jamesthebard@social.linux.pizzaIt's nice having the blog back up and running again. I ran into an issue running Gitea calling webhooks because it didn't trust my sketchy certificate authority. Not the most difficult solution, but having the blog back online means that I can fix it, then document it...and hopefully help someone out. #homelab
@nobodyinperson@fosstodon.org:gitea: #Gitea 'teams' are broken or I don't understand their purpose:
- you can't mention or even see teams you're not part of
- you can't mention a team in an issue where the team has no 'access' to the repo (although it still sees it without such access!?)
- BUT: the impossible-to-notify team is still auto-completed when composing the issue, but sil…
@ripienaar@devco.socialAnd finally the annoying thing that caused me to even look at ClouDNS. Now have a gitea action that runs acme.sh nightly to manage a cert, if it changes it commits it to my CM repo where I can deploy it using CM to multiple servers.
You can't using HTTP validation on multiple servers unless all in one location and behind some LB - so with this I can have small VMs everywhere serving the same thing with same cert.
@danirod@fosstodon.orgOver the lunch break, I made a backup and migrated my Gitea instance to Forgejo.
As the docs claim, fully drop-in. I didn't even have to rename my data directory from "gitea" to "forgejo", just swap the Docker container in the deployment and it's done. Backups have been tested, and data consistency is OK.
I've researched about why Forgejo exists and why it was forked from Gitea, and I fully agree with that.
@Mirk0dex@social.linux.pizza
@zimpenfish@social.rjp.isMigrated from Gitea to Forgejo. Their migration instructions didn’t work. Heatmap is broken. Organisation avatars are broken. Pages occasionally just don’t load. Some themes are broken. Not a great first impression!
@ripienaar@devco.socialThe day after I installed gitea - the fork didn’t seem enticing since it was a 1:1 fork - now they decide to go their own way.
OSS drama never ends sigh. Corporate owned OSS is just net negative despite a few shining good examples.
@nobodyinperson@fosstodon.org @danirod@fosstodon.orgI'm selfhosting all my dotfiles now in my Gitea instance and after configuring an avatar for each project, I think it looks neat and tidy. https://git.danirod.es/dotfiles
Since I'm the only user of my instance, I decided to use organizations as my namespaces. I created an org for my do…
@Mirk0dex@social.linux.pizza"git.mirkodi.eu", my Gitea instance, has finally shut down! It will now redirect to #Codeberg.
