# Self-Hosted Galaxy Packages in Forgejo Git server **URL:** \ **Category:** Project Discussions\ **Tags:** ansible-galaxy, galaxy-ng\ **Created:** [February 19, 2026, 9:09pm UTC](https://forum.ansible.com/t/self-hosted-galaxy-packages-in-forgejo-git-server/45369 "2026-02-19T21:09:38Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![eNBeWe](https://avatars.discourse-cdn.com/v4/letter/e/35a633/32.png) [@eNBeWe](https://forum.ansible.com/u/eNBeWe)\ **Post date:** [February 19, 2026, 9:09pm UTC](https://forum.ansible.com/t/self-hosted-galaxy-packages-in-forgejo-git-server/45369/1 "2026-02-19T21:09:38Z")
Hi, some of you might be familiar with the Git server Forgejo ([https://forgejo.org](https://forgejo.org)) (or the origin project Gitea). In case you didn’t know, there is a “Package Registry” feature integrated that allows hosting for build artifacts directly within Forgejo. Currently this allows for various different package types. Basically it is a small Nexus/Artifactory/etc. directly in the git server. I am proposing code changes to add Ansible Collections as a new supported package type and implemented that in Forgejo ([https://codeberg.org/forgejo/forgejo/pulls/8537](https://codeberg.org/forgejo/forgejo/pulls/8537)). Currently there is a roadblock in the process, because the Forgejo maintainers are not experienced with Ansible and need some more outside perspective to see if the feature works. So, if you would be interested in this feature, I would appreciate a bit of help testing this. There are some links in the pull requests with a testing instance. * * * A few points I have been asked repeatedly: - **Q:** Why not just use the collections from git directly? **A:** I don’t like the way the versioning works from git. It kinda replaces the versioning in galaxy.yml and only uses the commit information. Publishing proper collections forces you to work cleaner. - **Q:** Why not use Ansible Galaxy / Galaxy-NG? **A:** I like self-hosting my stuff. - **Q:** Why not use some existing solution like Nexus, Artifactory, ProGet or Pulp? **A:** Nexus and ProGet don’t support Ansible Collections, Pulp is either a monster (if running in full Galaxy mode) or a management nightmare, Artifactory is non-free, neither in the sense of freedom nor free beer. ---
**Author:** ![chris](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/chris/32/293_2.png) [@chris](https://forum.ansible.com/u/chris)\ **Post date:** [February 20, 2026, 2:47pm UTC](https://forum.ansible.com/t/self-hosted-galaxy-packages-in-forgejo-git-server/45369/2 "2026-02-20T14:47:05Z")
That’s a great idea, I might look at opening a feature request to add this to GitLab, the list of GitLab supported packages is here: > **[Supported package managers and functionality | GitLab Docs](https://docs.gitlab.com/user/packages/package_registry/supported_functionality/)** > > GitLab product documentation. ---
**Author:** ![Thulium-Drake](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/thulium-drake/32/833_2.png) [@Thulium-Drake](https://forum.ansible.com/u/Thulium-Drake)\ **Post date:** [February 27, 2026, 10:51pm UTC](https://forum.ansible.com/t/self-hosted-galaxy-packages-in-forgejo-git-server/45369/3 "2026-02-27T22:51:35Z")
Funny, I was looking up something different in the open PRs on Forgejo and I literally stumbled upon it. This would also solve a architectural thing for me, as I also like selfhosting my stuff and I know from experience that running Ansible Automation Hub (the downstream from Galaxy) is, and I can quote you on that, “very much not fun” 😉 We actually ended up ditching AAH, because we didn’t really use it enough for the amount of resources it wants to use. I will also reply on the PR, but yes, this is a great feature for in Forgejo’s Package registry and thanks for working on it!