Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On-demand crawling #10

Open
tomzx opened this issue Oct 20, 2016 · 2 comments
Open

On-demand crawling #10

tomzx opened this issue Oct 20, 2016 · 2 comments

Comments

@tomzx
Copy link

tomzx commented Oct 20, 2016

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.

@reiz
Copy link
Member

reiz commented Oct 25, 2016

Hi @tomzx. Are you using your own VersionEye instance? Like described here: https://github.com/versioneye/ops_contrib?

@tomzx
Copy link
Author

tomzx commented Oct 25, 2016

@reiz Yes. Sorry if that wasn't clear from my post.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants