This is on our list for an upcoming maintence release, and may get implemented in the next one. you can check the status of it at PG-1001. https://inedo.myjetbrains.com/youtrack/issue/PG-1001

There are many guides and ways to do this, please search "adding a maven artifact to a repository". Here is one such example: https://maven.apache.org/guides/mini/guide-3rd-party-jars-remote.html

Version 1.1.0 of the upack command line tool is now available from http://inedo.com/support/documentation/proget/reference/upack. The chocolatey version has been submitted and will be available once it's approved.

In this case, you will need to give the "Anonymous" access to push packages to the feed. You can configure this from Admin > Tasks.

Final results for curl -X PUT... I was able to change C:\Program Files\ProGet\WebApp\Web.config (yes, my server is on Windows 10), and increase the transfer size from 1Gb to 3Gb I then restarted the ProGet Web Service I then tried to upload a zip file 2.02Gb in size..and, it worked.

Apparently I was an idiot and couldn't do basic auth correctly, because once I did that correctly it worked fine without anonymous access involved. I am using Java 8, and the Authenticator class to set the authentication on my URL globally. Hope this helps the next person coming along.

I'm on ProGet Version 4.7.8 (Build 4) (locally hosted, not on EC2) and I'm able to upload universal packages to an S3-backed feed using the upack.exe tool with both the latest published release of the Amazon plugin and a debug build from source code. Can you still reproduce the error on the latest version of ProGet?

The endpoint is not yet deprecated. This error means that connector url is incorrect, npmjs.org is returning an error, or you have some proxy server blocking the request in between ProGet and npmjs.org.

This appears to be an internal Java error, indicating that the package cannot be bufered due to low process memory. So, I would increase the memory of your Java/Jenkin instance. You can use the -Xmx1024m option to give 1GB of memory to your application. This will increase the amount of data you can store in memory.

The npm endpoint to get all packages is /-/all, so in your case: http://dr-tj-pkgsvr01/npm/npm/-/all

Tried stoping the service that was tying up port 80. No help.

Ok, I noticed that in your log, npm isn't authenticating. Is the anonymous user allowed to access the feed in ProGet?

The native API is a database wrapper, and thus would only be able to return local/cached packages. You should consider using the NuGet API instead.

Team member here. I'd like to let you know that we've moved to the public npm registry. See Retiring the Progress NPM Registry.

As of v4, ProGet will no longer support packages pulling packages with dependencies from the UI. This is because it's "impossible" to do without visual studio's context (target framework, .net version, etc).

Well, for this, you would use the Download package endpoint There's a lot of guides out there on how to use cUrl (here's a good one), but a basic use would be... curl http://proget.local/upack/my-feed/download/my-group/my-package/1.2.3?contentOnly=zip -o my-package1.2.3.zip ... then you can just use unzip.

We have added these exclusions to the Web.config that we include with ProGet.

Hmm, sounds like a NuGet/VS bug... definitely worth sharing this with them!

Please request a key at My.Inedo

I solved this by configuring the URL including port number in the Advanced Settings at "Web.BaseUrl"