Otter, BuildMaster, Hedgehog, and ProGet for Windows all require any supported version of Microsoft SQL Server. So, 2017 would be supported, since Microsoft supports it still. 2005, however, not.

Hello Pedro, Docker feeds appear to have been missed when the api user was added for feed authentication. I've filed PG-1295 to fix that. ProGet 5.1.0 is not released on Docker Hub, but you can build the image locally with this command: docker build -t inedo/proget:5.1.0 --build-arg PROGET_VERSION=5.1.0 github.com/Inedo/proget-docker

Hello; Your best metric is going to be your users; if they're complaining it's slow, then it's probably too slow. My guess is that it's intermittant (during peak times). But in any case, it's not about the number of packages (a micro server can easily serve millions of packages nearly instantly), it's about the number of simultaneous connections (requests) to the server, and the features you've enabled (like license checking, etc). It sounds like you've got a single "2 core instance with 8gb of ram" server; while you can try to increase the hardware, the bottleneck is most likely network related; a single server might not just be enough to keep up with the traffic from your developers. Keep in mind that "plain old NPM" (i.e. registry.npmjs.org) runs on a massive, dedicated data center and is heavily cached (basically read-only). The ProGet Free to ProGet Enterprise article contains some general guidance that might help answer your questions: High Performance: 1 Server per 50 Developers. The network never slows down, never crashes. Average Performance: 1 Server per 100 Developers. The network slows down and drops productivity 10% on average during peak times daily. Acceptable Performance: 1 Server per 200 Developers. The network slows down and drops productivity 10-30% during peak times daily. Unacceptable Performance: 1 Server per 250+ Developers. The network is unstable and crashes. You can try disabling connectors, disabling license checking, disabling vulnerability scanning -- but those are really important features, so your best bet will be to plan for a load-balanced scenario.

That is exactly what I was looking for. Thank you.

The Release & Deployment API was added in BuildMaster v5.5 so you'd have to upgrade to use it. As for the /api/json page, it shouldn't require a key to view the methods so there's a bug there and I've added that to our internal issue tracker.

Thanks!!!!!! That will help a lot.

Unlisting requires that Feeds_DeletePackage is part of the task.

As of BuildMaster 4.9, many of the restrictions in the express edition have been removed. #####Features Available Only in Enterprise Edition (4.9 and later): Enterprise Support Active Directory / LDAP Integration #####Limitations of Free Edition (4.9 and later): 5 Users 10 Applications 5 Servers The following information is outdated, but remains for users of older versions. #####Features Available Only in Enterprise Edition (4.8 and earlier): Enterprise Support Active Directory / LDAP Integration Automated Promotion Requirements Change Controls Configuration File Templates Database Change Script Deployer Deployable Dependencies Group-based Approvals Multiple Active Builds Scoped Privileges Server Groups/Pools #####Limitations of Free Edition (4.8 and earlier): 5 Users 10 Applications 1 Automatic Build / application 1 Configuration Files / deployable 1 Database Connection / environment & application 3 Deployables / application 1 Workflow / application 3 Environments 1 Imported Deployable / application 2 Issue Trackers 5 Servers 3 Source Control Providers