I see, so you're saying that that the ReSharper client appears to not work with a ODATA/v2 API? In this case, this is most certainly a bug or a misconfiguration and you should share/communicate it to JetBrains.

There is virtually no support in commercial or open source private repositories for JSONLD/v3. While it's on our roadmap to implement, it wouldn't come until late this year... and obviously it would require upgrading your PRoGet server software, which many organizations don't like doing for at least 6/12 months after a release (especially for something like ProGet).

So, this would effectively makes ReSharper unusable for private extensions.

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 is by design; it is the responsibility of a package author to license a package, and make sure that it's a standard license. This way, automated licensing monitoring can catch it. However, as you've noticed, this isn't the case for a lot of open source packages.

So, in this case, you'll want to use a different workflow. Just create a "approved packages" feed, and promote approved packages into these feeds.

We don't test with this, but I looked at the website...

https://resharper-plugins.jetbrains.com/

... and it appears to be a clone of NuGet gallery. As such, it seems you can use this URL:

https://resharper-plugins.jetbrains.com/api/v2/

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).

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; it's hard to say what the particular issue was (perhaps, a temporary server outage), but you can always go to https://my.inedo.com/ and request a key then enter it in the installer.

I'm afraid Linux doesn't support Windows Integrated Authentication.

As a work-around, you can create a second site in IIS that points to the same path, but doesn't have Windows Integrated Authentication enabled.

Hello; it's not the drop path, but the package source path. You can set this in the ADmin > Advanced Settings, and also in each feed.

No problem, I've filed PG-1277 so we can make sure it's done everywhere!

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.

Hello; I've added a feature request for this.

There is no ability to do a "mass edit" like this I'm afraid.

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.

You can use Tasks (Admin > Tasks) to restrict who can access which feed. Once you've restricted a feed (i.e. not give permission to Anonymous), then users who access it will be prompted for credentials .

The "protocol/API" (ODATA vs JSON-LD) really doesn't make an impact on this.

In ProGet v5, NuGet feeds to in fact support SemVer2 packages. If you're finding errors, then you may have a legacy feed: please refer Legacy (Quirks) NuGet Feeds for how to migrate. Otherwise, if you have specific error cases that we might be able to try to reproduce, please let us know it.

Hi Josh,

Sorry, this seems to be a v6 glitch! But we're on it :)

I've submitted BM-3192 and then inedo-docs/#6 to update our documentation.

Your understanding of how the feature is supposed to work is correct, and your use-case is how it's supposed to be.

Thanks for reporting it !

hi Keith,

We definitely plan on having an offline process, and welcome your feedback on it.

You can read a bit about how the hub works (it's in beta, so please forgive the rough docs). Specifically, check out "Configuration and Offline Installs":

https://inedo.com/support/documentation/proget/installation/hub/inedo-hub

The Inedo Hub wraps Romp (more coming soon on that), so you could also use that to install ProGet as well, as a command line process.

Does that help?

You shouldn't be receiving a "401" error from the public npmjs registry. If you are, my guess is that you have some sort of proxy or firewall selectively blocking outgoing access to certain queries to the registry.

Once you resolve that, then p[roblem #2 will also be resolved.

We don't have any guides on this integration specifically, but the usual situation is that TC can't authenticate. The easiest thing to do is to allow anonymous publishing to the feed, but not overwriting.

Otherwise, you can try to get the authentication to properly work, which typically involves sending username/password or configurating an API key properly.