I can only select a single requirements file when importing from GitHub under the free plan.

[Former user]

After selecting requirements.txt on the staging branch I getting an alert with:

ERROR: The selected project file is in a private repository. Please upgrade your plan to monitor the selected project.

On: https://www.versioneye.com/user/projects/github/mediapop/landrover/show

[Robert Reiz]

That's not a bug, that's by design. If you want to monitor more than 1 file in private git repositories you have to by a subscription here https://www.versioneye.com/pricing. Somehow we have to pay the servers ;-)

[Kit Sunde]

You should specify it somewhere. The error message is confusing.

[Robert Reiz]

@kitsunde What error message would not be confusing? What message would be more clear? By the way, VersionEye is open source: https://github.com/versioneye

[Kit Sunde]

The error doesn't actually describe the issue. Since the free plan includes 1 private repository. The pricing page should probably mention it only covers 1 file for the free plan and the error message should probably be:

The free plan is limited to monitoring 1 private file.

[Robert Reiz]

@kitsunde OK. I just updated it to You reached the limit of your current subscription. Please upgrade your plan to monitor more files in private repositories..

[Kit Sunde]

Anyways since I have you on the line I have a followup question. Does that mean the term "project" on https://www.versioneye.com/pricing refers to a single requirements file? So for instance in any EmberJS project you'd end up having both bower.json and package.json which would count as 2 projects?

Most of our repos have ansible, a backend and a frontend totaling a minimum of 4 different requirements files.

[Miyata Jumpei]

@reiz > So for instance in any EmberJS project you'd end up having both bower.json and package.json which would count as 2 projects?

I have the same question. How about this?

[Robert Reiz]

@miyajan @kitsunde Hey guys. By default 1 VersionEye project represents 1 file. However it is possible to merge projects. Assume you have a Gemfile project a bower.json project, than you could in the settings tab of the bower.json project use the merge function and merge it into the Gemfile project. In that case the bower.json file would be a child of the Gemfile and in the project overview you would only see 1 project and we only count the parent projects for the pricing. In the project detail view you can switch between the files.

By the way, everything you see at VersionEye.com is open source. If you don't like the pricing model you can spin up your own VersionEye instance: https://github.com/versioneye/ops_contrib