composer / satis

Simple static Composer repository generator - For a full private Composer repo use Private Packagist
MIT License
3.14k stars 518 forks source link

Possibility to define options pro repository #123

Open gennadiylitvinyuk opened 10 years ago

gennadiylitvinyuk commented 10 years ago

It would be nice to have a possibility to define some options (for example required packages) pro repository.

This would simplify mirroring. Also it would speed up some operations - satis will not search for private packages in local repositories and in the other way.

For example this way:

{
    "name": "Company",
    "homepage": "http://packages.local",
    "repositories": [
        { 
            "type": "vcs", 
            "url": "https://svn.local.local/privaterepository/",
            "require-all": true
        },
        {
            "type": "composer", 
            "url": "https://packagist.org",
            "require": {
                "zendframework/zendframework" : ">=2.2",
                "monolog/monolog": "*"
            },
            "archive": {
                "directory": "dist/ext",
                "format": "tar",
                "skip-dev": true
            }
        }
    ],
    "archive": {
        "directory": "dist"
    },
    "require-dependencies": true
}

Global options (at root level) would be overriden by options on repository level.

nathanlenz commented 10 years ago

Yes! I'd love to be able to mirror a couple packages from packagist and require all from my private vcs repositories.

nathanlenz commented 10 years ago

One way to do this would be create two private repositories.

  1. Mirrored repositories requiring specific packages.
  2. Private VCS repositories using "require-all".
alcohol commented 8 years ago

Isn't this already possible? /cc @Seldaek

Seldaek commented 8 years ago

options for repos is possible, satis options per repo isn't I guess.