Skip to content

On-demand crawling #10

@tomzx

Description

@tomzx

Hello,

Here's my current use case: I use versioneye to track the dependencies of internal projects (mostly PHP-related). Obviously we do not use all the packages available on packagist. We would also like not to depend on VersionEye public API to obtain packages information. However, crawling all of packagist while we're probably interested in 500-1000 packages seems a bit excessive.

Thus, it would probably make sense to have tracked projects dictate which packages should be crawled. Then, the crawler/producer would only have to walk through these packages in order to fetch a minimal list of metadata.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions