I'm not familiar with Zabbix, but there are two things you can do to check about the status of the components (Database, Web, Service): If the database (SQL Server) wasn't working, or there was a problem with the website configuration, then visiting / will yield a 500 or some other not available message. You can just query the ProGet service run state directly. You could parse the text on the /connectors page or use the native API to get a status of the connectors.

This will be addressed in next maintenance release as PG-1294 . As a workaround, you can access the package directly by version number even without this fix.

Your best way to do this, would be to use the nuget client, and then pull the cached packages to your feed. "Pulling with dependencies" as a feature in ProGet would require implementing every dependency resolution algorithm of every version of every client, including the non-deterministic dependency resolution used by the npm client, and then somehow letting you select the algorithm version and the additional content required by the algorithm (such as .net framework target version).

Thank you Alana. That worked.

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

The Inedo Hub is still in Beta, but we plan to have it support individual components of a tool, such as ProGet.Web. You will also be able to do something like, romp install ProGet.Web to just install/configure the web package. We're also going to be shipping the "legacy" installer (probably won't call it that ^_^), as an alternative option for people who set up automations. For now.. you can use same process.

Use permissions for this. There is a Feeds_OverwritePackage task or something that you can remove, or restrict as you see fit.

Hello Ludovic, This appears to happen when there is no version of your package tagged as latest. To fix it, click the Edit Details button on the latest version of your package and add a tag named latest (all lower-case). I've filed PG-1279 to fix this happening in the first place.

Hello Timofey, I've filed PG-1280 to hide the build metadata from NuGet version numbers when they are displayed in titles.

I had to update the NuGet feeds to the latest version after the upgrade. The packages are pulling in now.

This will be fixed in PG-1273 for the next maintenance release.

Hi, I have tested with npm and all is working now. Thanks very much. Regards Fabrice

Hello Attila, This is indeed a bug. I've filed PG-1272 to fix this.

Hello Jasper, I don't have a Linux installation of ProGet in front of me, but it's possible that this would work if you renamed the feed to dspdocker (with no capital letters).

I can answer the first three questions pretty easily: ProGet does not support being installed as a sub-application; some users have done a reverse proxy successfully, but we really don't support that configuration The Feed url is based on the name of your feed, so it can be whatever you want. You can't do further customization. That's not a problem But I'm afraid I really don't understand the situation about 4-6. ProGet does have some extensibility hooks that you may be able to use.

unfortunately this bug fix just missed the cut. But we will ship it in the next maintenance release, likely in a couple weeks. It's not scheduled yet.

Hello, Ben. Thank you for your reply. Test result is as you expected. The icon issue was solved after I changed backslash to forward slash. Regards.

Based on the URL -- you must have created a Universal Packages feed. You'll need to create a NuGet feed.

Hello; Inedo.com currently seems to only communicate over TLS1.0; I don't have a timeframe for when that will be upgraded, but I want to add that we don't have any secure or sensitive information on inedo.com anyways. In the case of LDAP, it seems to me that there is some sort of issue with the LDAP code mapping your username. AD configuration can be very complicated I'm afraid, and it will involve a bit of back-and forth, with sharing potentially sensitive or company-identifying information. When you search for a user in ProGet, you will see a log of the domains, etc., being searched. Ifyou can publish that to a ticket, then we can investigate further.