gogs / gogs/gogs

Feature: expose repo as composer package.

Open
#2,507 16 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

☁️ plugin 🎯 feature status: await
Dominant language
Go
Stars
47.8k
Forks
5.1k
Avg merge
7h 23m
Merged PRs (30d)
5

Description

I've seen over at GitLab that someone is in the making of Composer Service, that makes it possible to expose a repository, as a Composer package for PHP.

That would be a pretty cool feature, if you'd like to host your own private packages. Atm, it's possible to have a static package repo, by using the static repository generator Satis.

Furthermore, support for npm packages or ruby gems, could also be possible.

Actually when I'm thinking about it, these features might not belong to the Gogs core, but maybe as some sort of plugins/add-ons, as mentioned in #2438

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the proposed Composer Service and Satis links in the issue, then read #2438 for the plugin/add-on context. No Gogs files, tests, or entry points are named; first define whether Composer, npm, RubyGems, or an extension mechanism is in scope, and document the resulting package-hosting requirements.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, javascript, php, ruby
Domain
backend, devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.