Hello Rickard, The official installation guide creates a volume using docker run -v. You can also extend the ProGet image like this: FROM inedo/proget:5.0.9 RUN mkdir -p /var/proget/extensions RUN curl -sSL -o /var/proget/extensions/InedoCore.upack \ https://inedo.com/den/feed/download/inedox/InedoCore/1.0.3 && \ echo "14f4df63af7b8991390cf77d1f68be55569609f4 *InedoCore.upack" | sha1sum -c (The checksum part is optional, but it will cause the image to fail to build if the file isn't what was expected, which gives you a better guarantee that the same image will be built every time.)

Hello Rickard, This is PG-1212 and will be fixed in ProGet 5.0.9.

Unfortunately it's impossible to say. The error message you have provided is in complete, and doesn't give any information about the problem. Scoped packages works in testing, and we haven't heard issues from othere users about it. You'll need to do some further debugging and provide some more information for us to further help you.

If you go to the "Packages" page, you can see packages in ProGet. The feed view will always aggregate your connectors; so if you don't want to see the aggregated (remote) packages, you'll need to disassociate the connectors with the feed.

Because of a reinstall of proget with an existing database the package paths were resetted to default. After fixing the paths, the error went away. The error should be more descriptive when the files can't be found on file store.

Thank you, I was not aware of this. Seems to work

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.

Looks like this was answered here: https://inedo.com/support/questions/8233 5.0.8 fixes the issue.

Hi, Please refer the below blog. You may have an idea on Semantic Versioning. https://www.meritedin.com/robust-api.html Please don't forget to take a look on the videos listed on their playlist.

Ok got this working by removing the api key in the feed properties, thanks!

In the post you linked, the problem was the host operating system (Ubuntu 14.04). So you should upgrade to 16.04.2 LTS. If it's not working, then you'll likely need to explore the docker script, and step into the container to see what specifically is the issue.

As a followup, support for the Portable PDB format in the symbol/source server has since been added to ProGet.

This error indicates an incomplete request is being sent to ProGet; typically it happens from misconfigured client that is not authenticating properly.... but it's really hard to guess from that error message alone. Unfortunately I'm not familiar enough with how to configure TeamCity to advise on how to fix this. Perhaps cross-post this on their support forums as well.

Hi Tod Thanks for the fast response. Since i am not relying on the statistics of Proget i have solved the issue with a bit of work. Created new feed that uses new standards setup custom feedpath and droppackage path for bulk import on the server i located that packages on the filesystem and dumped into the appropiate bulk import folder. wait a minute or two and the new feed has all the packages. Rename feeds so the new one has the name of the old deprecated. It is a workaround but it works but again - you loose statistics. Symbols and Source seem to survive :-D

This will be fixed as part of PG-1204 in v5.0.8 - due out early next week.

Thank you for the report - it appears the uninstaller is relying on a configuration value that does not exist; the uninstaller will be fixed in v5.0.8. For reference, here is a quick summary of what the uninstaller does: (IIS only) delete ProGet application pool (IIS only) delete ProGet website stop & delete INEDOPROGETSVC and INEDOPROGETWEBSVC Windows services delete %ProgramFiles%\ProGet directory delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ProGet hive from registry (optional) drop ProGet database (optional, SQL-install only) uninstall SQL Server 2016 from "Add or remove programs"

You can uninstall, then reinstall. If you follow KB#1013, and make sure to keep the application pool and websites names as specified, then the installer will detect them next time and upgrade as needed.

This is a "false positive"; https://inedo.com/support/kb/1113/anti-malware-false-positives-code-signing-and-safety-of-inedo-products Please report it to Cylance

Alana, I tested the change and it is working for me with version 5.0.8. Ship it! :)

The issue is related to packages missing SHA1 hashes in the ProGet databases; at some point packages were able to be added without them. We have updated the migration process internally to perform them if they are missing, and this fix will be included in the next maintenance release. Here is the tracking issue: https://inedo.myjetbrains.com/youtrack/issue/PG-1203