Hi @Dan_Woolf , Thank you for your message. We've updated to the most recent version from 2023.16 to 2023.18 and I can confirm that this is now working! Thanks!

Hi @Evan_Mulawski_8840 , That particular bug may be resolved by running the patch script attached to this upcoming change: https://inedo.myjetbrains.com/youtrack/issue/PG-2484 As for retrying the migration; there will be a button on the ProGet root page if there is a failed/incomplete migration (/) that allows you to retry it. This will open to the /retry-migration URL, which I would recommend using instead of a database insert. Best, Dean

Hi @w-repinski_1472 , Based on your initial usage, I think SQL Server Express will suffice. The ProGet database is basically a package metadata index, and essentially stores things like package name, version number, and a variety of things including the manifest file (.nuspec, package.json, etc). It's maybe a few kb per package, and you'll need 100k's of packages to even reach 1GB of metadata storage. In your information you state that network connections are the bottleneck. I don't understand this completely in times when we have 100G cards, maybe I don't understand the scale on which ProGet is used in other companies. The issue is with the number of connections, and a single server struggling with 100's of expensive queries/requests per second. Running "nuget restore" or "npm restore" will hammer the repository with 1000's of simultaneous requests, and many of those need to go to nuget.org or npm.json to be resolved. When you have multiple users and multiple build servers running these kinds of restores, then you run into load issues. At about 50 users, a load-balanced / high-availability cluster starts to make sense. After 250 users, sticking to just a single server doesn't make a lot of sense (cost of downtime is expensive). Once you need a server cluster, then upgrading SQL Server would probably make sense. There's a big cost difference between a single server and a server cluster - in part the ProGet licensing fees, but also managing a server cluster is more complicated. Some organizations prefer to start with high-availability right away rather than worry about upgrading later. See How to Prevent Server Overload in ProGet to learn more. hope that helps clarify! Best, Steve

Hi @hashim-abu-gellban_3562, Due to some reasons I don't fully understand, authenticating to the Docker API requires using a Bearer authentication token Authorization: Bearer {token} Here is an example for how to get that token: function GetDockerToken() { param ( [string] $packageName = $(throw "-packageName is required. This is the namespace and image name. For example: library/my-container-image"), [string] $feed = $(throw "-feed is required"), [string] $actionToAuthorize = $(throw "-action is required. This is the docker action to be authorized (pull, push, delete, etc)"), [string] $apiKey = $(throw "-apiKey is required"), [string] $progetBaseUrl = $(throw "-progetBaseUrl is required. "), [string] $service ) if ($service -eq "") { # This expects that $progetBaseUrl is prepended with "https://" If you are using "http://" then change 8 to 7 below. $service = $progetBaseUrl.SubString(8,$progetBaseUrl.Length-8) } $base64AuthInfo = [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes(("{0}:{1}" -f "api","$apiKey"))) $response = Invoke-WebRequest -Uri "$progetBaseUrl/v2/_auth?service=$service&scope=repository`:$feed/$packageName`:$actionToAuthorize" -Headers @{Authorization=("Basic {0}" -f $base64AuthInfo)} if ($response.StatusDescription -eq "OK") { $token = ($response.Content | ConvertFrom-Json).token $token } } I know we plan to document all this better some day, for now you can find the Semantic Versioning for Containers page. Dean

Hi @Stephen-Schaff, Thanks for the detailed write-up; the behavior you describe makes sense, and made for very copy/pasting PG-2478 :) We anticipate getting this in the next maintenance release, scheduled for Sept 15 Best, Dean

Hi @cimen-eray1_6870 , Great questions; there's no problem having a second instance with ProGet Free Edition. The relevant restriction is that you can't use a Connector in ProGet Free Edition to connect to another instance of ProGet (either another Free Edition or your paid edition). Hopefully you can use your Maven feed as a proof of concept for implementing it in the main instance. Good luck! Cheers, Steve

Hi @gdivis Thanks for the update I moved to docker recently - much more flexible than Microsoft

@atripp Good to know Thanks

I added this to our Otter 2023 list of items to review/consider :) Please stay tuned

Hi @en_1446 , Not sure what version of ProGet you're using, but this seems to be on the recent versions I've seen, so I would recommend to upgrade :) Cheers, Alana

@atripp said in BM - Help needed for Git checkout: shexec echo hello world; I have no issue to run a shexec. This is just the git-checkout. The server is also configured thru Otter without any problems ... I am using artifact captured from localhost so it is OK for me I will make other tests later

Hi @kichikawa_2913, You can ignore the Age field; it's just used internally by Visual Studio, along with the Id. Not sure why, but it's a strange value in PortablePDB files. Here's more on what Age means if you're dying to read PE-COFF specifications https://github.com/dotnet/corefx/blob/master/src/System.Reflection.Metadata/specs/PE-COFF.md#codeview-debug-directory-entry-type-2 Best, Alana

Thanks, I updated and feed cleanup is back to seconds instead of hours [image: 1692943179937-5b6aebe8-48a0-410b-bc47-c5d54f86e8f6-image.png]

@apxltd I'll wait for v2024

Hi @atripp Oups, After your reply, I checked the ssh config on the target server and I forgot I allowed ssh root connection only from the Otter / BM server. Match Address XXX.XXX.XXX.XXX PermitRootLogin prohibit-password Changing the address solved the error My bad Thank you for your time

Hi @ccordova_8628 , ProGet requires SQL Server; Postgre/MySQl are not supported. Cheers, Steve

Hi @ivan-magdolen_6846, It looks like you're on the right track with finding the XML for that key. Since you're automating the installation, and already have DBO access to the ProGet database, I would suggest just directly adding it to the database using that stored procedure. You can also add/edit some values (like license key) if you want to the Configuration table. Alternatively I guess you could try Admin:Admin as the API key, since that account will be created by default. I'm not sure if it will work with the native API however. Best, Alana

Thanks Steve, That was helpful! Regards, Priyanka

Digging more into this, it appears that "pip search" is basically unsupported at this point, even by pypi.org. You can disregard this issue.

Thanks! Merged and released.