Problem
For organizations that have separate means of securing the service, or for those that want to self-host without actually needing data privacy, it would be nice if there was a toggle to enable anonymous pulling, like Packeton does with anonymous_access and anonymous_access_archive.
Proposed Solution
Add a toggle that disables the need for composer authorization information on pulls.
Alternatives Considered
For now, you can add a Varnish service (a reverse proxy like NGINX would work as well) to the docker compose layout, then route traffic through that with a receive hook adding an Authorization: Bearer <> header.
Additional Context
No response
Problem
For organizations that have separate means of securing the service, or for those that want to self-host without actually needing data privacy, it would be nice if there was a toggle to enable anonymous pulling, like Packeton does with
anonymous_accessandanonymous_access_archive.Proposed Solution
Add a toggle that disables the need for composer authorization information on pulls.
Alternatives Considered
For now, you can add a Varnish service (a reverse proxy like NGINX would work as well) to the docker compose layout, then route traffic through that with a receive hook adding an
Authorization: Bearer <>header.Additional Context
No response