Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gitea as Package Registry Reverse Proxy #23619

Closed
uvulpos opened this issue Mar 21, 2023 · 1 comment
Closed

Gitea as Package Registry Reverse Proxy #23619

uvulpos opened this issue Mar 21, 2023 · 1 comment
Labels
issue/duplicate The issue has already been reported. topic/packages type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@uvulpos
Copy link

uvulpos commented Mar 21, 2023

Feature Description

As a team with plenty of fetches from external servers like dockerhub, composer or pip, especially now with the CI/CD pipelines, I would suggest adding an optional proxy for these package registries.

The huge advantage of this would be, that the build + delivery speed inside a company would improve, but also less international internet traffic would occur, if certain servers are e.x. only in one country given.

A busy CI/CD pipeline could also try to prevent an external registry call and map it to itself to fetch the cached resource. But this should be a check and not checked by default imo 🤔

I could imagine that a server administrator could either whitelist a couple of packages to do this, but also by giving it a limited amount of disk space, and he caches everything himself from registry xyz.

The urls could look like this:

http://my-domain/package-cache/<registryname>/<organization>/<package>

http://my-domain/package-cache/dockerhub/gitea/gitea

http://my-domain/package-cache/composer/phpmailer/phpmailer

http://my-domain/package-cache/ghcr/linuxserver/wikijs

What do you think? Could that be a feature for 1.20 or 1.21? 🤔

Screenshots

No response

@uvulpos uvulpos added type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. labels Mar 21, 2023
@KN4CK3R KN4CK3R added issue/duplicate The issue has already been reported. topic/packages labels Mar 21, 2023
@KN4CK3R
Copy link
Member

KN4CK3R commented Mar 21, 2023

Duplicate of #21223

@KN4CK3R KN4CK3R marked this as a duplicate of #21223 Mar 21, 2023
@KN4CK3R KN4CK3R closed this as completed Mar 21, 2023
@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/duplicate The issue has already been reported. topic/packages type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

2 participants