Skip to content

Dynamically provide composer packages #34248

Open
@chascode

Description

@chascode

Feature Description

Hi,

As an alternative approach to composer's package registry, I request composer packages are dynamically generated on demand.

For example: Suppose I go to "https://gitea.example.com/composer/p2/foo-vendor/foo-package.json" (as the composer client might), gitea could generate a response according to that repository's tags, branches and composer.json files.

No need for scripts that generate tarballs before uploading them to gitea, or using far easier alternatives such as satis (with ugly webhooks). A simple git commit/tag/push and composer packages could be installable without extra work.

Screenshots

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    topic/packagestype/proposalThe new feature has not been accepted yet but needs to be discussed first.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions