Just to give you a heads up. I'm already on version 2023.32 and it works like a charm. Thank you.

Hi @atripp, Thanks for the response! It turns out I was overlooking the fact that the docker container cannot access the files of the host. So the directory was non-existent from the perspective of the ProGet instance. I ended up solving the issue by copying my bulk import directory into the docker container itself, which allowed the bulk import service to detect the directory.

@shfunke_1795 @jrottmann_6111 @sdohle_3924 @bahues_9728 @appplat_4310 Thanks for insight into this! I'm happy to report that starting in ProGet 2023.22, you can create Alpine (APK) feeds with connectors :)

Hi Jared, According to the docs - It’s currently not possible to mirror another private registry. Only the central Hub can be mirrored. However, we do support connectors to another repository and are nearing completion on a project for docker replication between ProGet instances. Thanks, Jason

Hi Paraig, Replication between two different versions will likely work, though it would be a good idea to verify correctness when complete. We try to maintain backwards compatibility though we don't officially support this scenario (by this I mean we don't routinely test replication with older versions). In the event of a problem, another possibility is to replicate to another 4.6.7 instance, and then upgrade it to the latest version.

Thanks very much, Scott. You helped me by mentioning that the feeds themselves also need to support SemVer 2.0. I wasn't aware of that fact. So I just migrated our feeds an now everything works fine.

Hi Ryan, Sorry for the delay in getting back to you - we're planning to add this to ProGet 5.2, which currently has a release date of April 11. It should be included in Inedo SDK 1.1.2 (see tentantive spec here). Does that look like it will cover your situation?

Upgrading to v5 seems to have fixed this

If you want developers to always be able to use any version of a package, then you should configure a connector to that remote resource. Then, they will always be able to download the latest version of the packages they need, and ProGet will cache those packages.

There was a UI change; these are listed under "Containers" in the top UI.

These will be included in the next maintenance release as per this issue: PG-1406

This is a feature of the paid edition of ProGet; once you have that, you can scope security tasks to specific feeds. Otherwise, everything is global.

It's fixed. Not only that, but listing the packages also seems faster. Thanks!

It was my reverse proxy (apache). I had to set AllowEncodedSlashes to On. Problem solved.

This is available in a standard installation of the latest version under Manage Feed: I'll check out the source code now. Thanks.

Hello Tobias, PG-1270 will make local packages appear before remote packages in the list, as well as making connector packages appear in the same order that they would appear in the connector.

Haha, I missed it by one minor verison. :-D Sounds good. Thanks for the quick response. Means I get to test my scripted upgrade process. :-D Have a good one.

It's a "401" error, which means "not authorized" In this case, you could have the wrong credentials in Yarn (or no credentials). Note that "Windows Integrated Auth" is not supported by npm or yarn.

The Integrated Web Server doesn't have many features, including request logging and tracking. So in this case, you'll want to upgrade to IIS: Please refer to KB#1013: Hosting Through IIS Instead of the Integrated Web Server

The "remote icon" means that there is a package entry in a remote server. If you're continuing to see it, then it may take a little bit for the connector metadata (in memory)cache to be cleared. You could always stop/start the webservice, and then this will go away.