Topics created by steviecoaster

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

Ha, It was a goofy issue. I wasn't paying attention and had the Body defined as a string in my proxy function. This is working nicely now!