Recent searches
Search options
Administered by:
#gitea
Super happy I finally have my own Forgejo instance, been wanting to host my own code for a while now.
Here are my dotfiles as a celebration: https://git.buduroiu.com/bruvduroiu/dotfiles
This important update includes essential fixes and improvements—upgrading ASAP is highly recommended for all users!
GitNex 8.0.3 is out with fixes for a few bugs that affect all users. Update when you can. :)
- Fix offline cache affecting online activities
- Fix glide for self-signed certificates
Anyways #askFedi what kind of protection would you recommend? We're opting for solution that's quick and easy to implement and lightweight.
@seanfobbe personally I'd consider #gitea and #SelfHosting.
- As of now I abude #github as free, #DDoS-protected hosting and something #Microsoft burns money in.
Once any of my projects would gain traction I'd move from there away.
- I just am not a huge fan of @Codeberg even tho they are a better option.
I jist move to either SelfHosting or nowhere...
Hm... so this new AI thing from @gitea ... it's definitely interesting, and many people aren't reading, again.
So, what did they do?
They basically created an API client that is usable for LLMs - meaning that LLMs can now directly interact with Gitea. It's not integrated into the server by itself, and nobody is required to use it. Basically, it's HTTP 
Also, this client by itself doesn't crawl other sites / uses data that was crawled from other sites, since it's literally just an API client.
BUT (!) you have to use an existing LLM model using a client (e.g. Cursor) to be able to use this API client. Now that's the interesting part... I don't know if there's actually a good LLM that only learned from data that it was allowed to use. This means, that Gitea kind of promotes using LLMs that crawled people's sites without their permission.
Sadly, the screenshots shown in the blog post by Gitea don't show what model they are using, so we can't tell if they are using a good or a bad model. (Though, I'm not sure if we specifically need to know that in this case.)
Anyway, I'm always happy to see people switch to @forgejo. I, personally, used it almost since I started moving away from GitHub / -Lab and I love it. Sadly, I know a few people who can't yet move to Forgejo since they're using architectures that Forgejo doesn't build for docker yet.
For those people who are still angry and "need to" be aggressive towards the devs: Calm down, maybe read my blog post that I made in collaboration with Finnley about outrage (https://steffo.blog/outrage-warps-reality/) and have a great day. Maybe go for a walk outside?
Anyway, have a lovely day! 
Many universities and research institutes have their own #Gitlab or #Gitea instances, which is a good thing. But are there any plans for these instances to be federated ? It's a bit cumbersome to open a new account on a new instance every time I want to collaborate on a project. #openscience
GitNex 8.0.1 is out to fix a few bugs including offline mode.
I follow one dev because of interesting thoughts, ideas and realisations. One of them were about git repositories
https://bacardi55.io/2024/07/26/re-thinking-my-git-hosting-with-sourcehut-and-forgejo/
And start to think about my current situation. Some years ago I moved from github to #gitea 
and later switched to #forgejo 
. This is for my projects where issue tracker if is used it is only for me.
Now I think about some RFC as idea and there are possibility that I will need (or want) to allow comments|issues|PRs. My Forgejo is w/o registration now. Is there some kind of best practices? Do you use sourcehut|codeberg|gitlab or something else together with #selfhost git?
If you, like me, are incredibly excited by this wonderful news, know that —at least for now— you can disable all this #Copilot crap by visiting https://github.com/settings/copilot and switching all the options to Disabled/Blocked. Perhaps especially the on-by-default "Allow GitHub to use my data for product improvements" one.
Thanks to #GitHub for reminding me how glad I am for #SelfHosting my own #Gitea #Git #Forge. If you're not already, maybe consider it or a (partial) move to #Codeberg too. It's great!
among other thing #gitea does give something unique , armored #ssh sig , when they need not map to a #gpg key
https://www.techaddressed.com/tutorials/add-verify-ssh-keys-gitea/
Anche Organic Maps, l'app #opensource per navigare senza tracciamento, abbandona #GitHub di Microsoft e sceglie piattaforme self-hosted. Un segnale forte: sempre più progetti scelgono autonomia dai #BigTech.
Part of my project for adopting gitops in my homelab has been setting up git hosting. I've selected Gitea for this instead of Gogs because I thought I'd have an easier time bootstrapping fluxcd...
Now that I've had more time to sit with the docs and learn more about Gitea, I've noticed they have broad support to serve as package registries too! It seems like I can host helm charts and docker images alongside my infra as code! This is fantastic, it'll greatly simplify my architecture. Two birds, one container!
Hi everyone, GitNex 8.0.0 is now out with numerous new features and UI refinements.
- User activity heatmap on the profile
- Dependencies for issues and prs
- Tracked time for issues and prs
- Search within files
- Filter issues by labels
- Filter issues where I am mentioned
- and more...
It's time to update! 
Release notes: https://codeberg.org/gitnex/GitNex/releases
Arghhh...
Deploy #gitea with official helm chart, using built-in sshd 
Create ssh keypair with appropriate type and key size
Added public key to my gitea user account
Key is listed in the UI, fingerprint matches
Run the cron to sync authorised_keys
Nothing evidently wrong in gitea logs
Modify local SSH config just to be REALLY sure it's supplying the correct key
Push updated branch and... It asks for git's password 
Exec'd into gitea server pod, can't find authorised keys file anywhere... It didn't bother to create it? It didn't notify me in the web UI that something failed when I synced the keys via cron?