Description
Feature Description
We at our company have a lot of organizations and the repositories are getting a bit cluttered due to the fact on how we use gitea.
We have for example a repository called firewall installation. Intended to make our installations easier. The organizations consists. of something like:
firewall-install
firewall-configfiles
and so on.
When a user goes into firewall-install and launches a script it either curls from firewall-configfiles or does a git clone as well does either curl or clone from other repos.
What the user does not need to see are the repositories that the firewall-install scripts uses it only confuses the user. He does not need to see the repo "firewall-configfiles" and what else there might be there. But the firewall-install script needs to be able to either curl or clone "firewall-configfiles" as was it a public repository "even though invisible" so that the firewall-install script can pull these things without using a password. So the repository is invisible but acting like a public repository.
Another example:
We have a lot of automated scripts for like installing Zabbix, Dokuwiki, Focalboard and so on all running on Nginx.
Therefor we have a nginx repository consisting of like
nginx-install
nginx-configuration-files
nginx-snippets
nginx-cloudlfare-ip
So when a user has to install i.e zabbix. He also can see alt the repositories that he does not net to know about. Al the user is interested in is dokuwiki-install whether that script pulls some configuration files or snippets the user does not need to see or be aware of as the end user will get confused on what or where to go.
This is not to hide obscure code as people are free to see the "Top Layer" script pulling the other repos or curling them the code is there as the clone it down they can just view whats happening. Its just to minimize clutter.
Basically we are looking for something like this (I tried to make a Mok Up) and attached it as a screenshot. Hmm which is not working.
So it goes something like this.
Visibility [ ] Make repository private
Visibility [ ] Make repository public
Visibility [ ] Make repository public but hidden from public view
If we make these "Additional files repositories private" the top layer script needs a password to download them this is what we are trying to prevent. the "Additional files and repos" are not secret but inconvenient when we wish to include simple tasks as curling a "non-visible" repo or cloning a none-visible repo.
Thank you for your time.
Oh the screenshot got uploaded I must have had some latency :-)
Oh and yes we could go "Puppet" or "Ansible" or what else is out there, but our company is not there yet :-)
I hope all of this made sense.