Hi @imm0rtalsupp0rt , We've published a version of the article now: https://docs.inedo.com/docs/proget/feeds/chocolatey/howto-chocolatey-proxyccr Let us know your thoughts or freel free to submit a PR should have have any suggestions! Thanks, Alex

We have the full gamut of environments. Those with unfettered access to the unwashed internet, proxied environments, a single machine with access we can tunnel through, to, yes, SCIF-levels of lockdown. In all of those scenarios, we offer an offline prep script that bundles everything needed for the installation into a zip file, which you can then sneaker-net into the environment and continue the installation. I think we can make the offline installation work based on what I'm seeing in the documentation. I just wanted to make sure it was a "supported" mechanism of installation.

Hi @steviecoaster , Nice suggestion; I made a small change and you can now do pgutil apikeys create feed --feed=* to create such a key. Thanks, Alana

Hi @steviecoaster , FYI - I just a note to the license restriction page; it looks like we don't mention the restrictions on other APIs (delete, scan, etc), but it's something we'll consider next round of docs refactoring. I know we do call it out on the main documentation pages though.

I would like to deploy Proget behind the an Entra App Gateway but I am unsure how to configure the gateway.

@steviecoaster the Native API should provide access to all of those procs FYI

Hi @steviecoaster, Thanks for the find. We'll get this fixed in the next maintenance release. Thanks, Rich

Late reply (was out at a conference), but this was in fact permissions related. I've added a check to ensure the Inedo service account has been granted modify permissions on the drop path upon creation, and it is working appropriately!

Hi @steviecoaster , You can use pgutil for this: pgutil settings set --name=Licensing.Key --value=XXXXXX This is in the Configuration table FYI, which is what pgutil settings does Thanks, Steve

Thanks @dean-houston! That's good enough for me. Looking forward to trying the new migrator once it lands, sounds really really good!

Awesome! Thanks for the quick response on this one!

Hi @steviecoaster, Thanks! We will take a look as soon as we can! Thanks, Rich

@steviecoaster great news, glad you got it all working

Thanks @steviecoaster! All that sounds great, especially since it won't require changing anything on our end :) Much appreciateD!!

Hi @steviecoaster , Very cool, looking forward to the packages! Here is the URL for the ProGet license agreement: https://inedo.com/proget/license-agreement The Inedo Hub does not have a separate license agreement, we just consider it part of the product; so you can just use ProGet's: https://inedo.com/proget/license-agreement Thanks, Nanci

Hi @steviecoaster , The Native API can be a little finicky, especially since you can invoke with JSON, forum-encoded values, querystring, and I think even XML. But it sounds like you're on the right track. Let me share the C# code that ProGet uses to set the password: using (var rfc2898 = new Rfc2898DeriveBytes(password ?? string.Empty, 10, 10000, HashAlgorithmName.SHA1)) { var bytes = rfc2898.GetBytes(20); DB.Users_SetPassword(userName, bytes, rfc2898.Salt); } ... it looks a little different than the code you're using, so hopefully that will help! -- Dean

@dean-houston thanks for that info! I think that'll do nicely. I'll have to play around with it to be sure, but from what I can tell it looks straightforward to implement. Thank you!

@steviecoaster great, thanks for sharing! I added this to our documentation (https://github.com/Inedo/inedo-docs/pull/253), but apparently I don't have ability to merge PRs in that repo so it'll go live sometime later I'm sure

Hi @steviecoaster , Sorry about giving the bad advice there -- I did not realize that the offline installer does not include the hub.exe program. It looks like the Offline Installer Creation Process must strip that from the offline installer we provide. As you discovered, the advice from before wouldn't really work. Without doing a deep dive in the code, I don't know how to make it work. This isn't a use case we designed for, and I'd hate to send you down a wild goose chase. How about just using our standard silent installation approach, which I shared before: # create working directories mkdir C:\InedoHub cd C:\InedoHub # download and extract file to working directory Invoke-WebRequest "https://proget.inedo.com/upack/Products/download/InedoReleases/DesktopHub?contentOnly=zip&latest" -OutFile C:\InedoHub\InedoHub.zip Expand-Archive -Path InedoHub.zip -DestinationPath C:\InedoHub # perform silent installation hub.exe install ProGet:5.2.3 --ConnectionString="Data Source=localhost; Integrated Security=True;" This will basically install the desired version and it's likely "good enough" for the time being. -- Dean