Topics created by forbzie22_0253

@forbzie22_0253, From an API standpoint, I believe only npm packages support server-side tags. Rubygems might, but in any case we strongly advise against using them: https://blog.inedo.com/npm/smarter-npm-versioning-with-semver/ Server-side tagging is not likely something we will support in the future. Deprecation and Listing are really only there because many of the client APIs support them. I'd need to see a strong, specific use case. If it's related to quality (e.g. dev, staging, prod), then it's a "hard no" because our solution to quality is prerelease version numbering/tagging with repackaging. I do know that Sonatype Nexus has always supported tagging, but their repository is more of a "fileserver with server-side metadata" and ProGet is package-based. The only documented use case they have for tags has been quality, and our solution/approach is far superior. Cheers, Alex

Hi @forbzie22_0253 , We have never seen a case where changing an IIS setting has benefited performance in any way whatsoever; instead we have only found headaches and problems from users modifying them. Those settings are not designed for modern .NET applications, but for like .NET Framework, classic ASP, etc. So please don't touch them :) Thanks, Alana

Hi @forbzie22_0253 , That's not exposed in the UI at this time; is there a reason/use case you'd want to use it? it's primarily intended as a kind of backup of sorts. Thanks, Alana

Hi @forbzie22_0253 , Yes, we use Kestrel under the hood. You can configure HTTPS under Admin > HTTPS: https://docs.inedo.com/docs/installation/installing-on-iis/installation-windows-https-support No real "gotchas" -- but note that with port sharing (i.e. binding to a hostname as opposed to an IP), that needs to use the HTTP.SYS component of Windows. Cheers, Alana

Hi @forbzie22_0253, The easiest solution is to change both the "ProGet Service" (INEDOPROGETSVC) service and the "World Wide Web Publishing Service" (W3svc) to Automatic (Delayed Start). This typically allows SQL Server to start before IIS and the ProGet Service start. Thanks, Dan

Hi @forbzie22_0253, There's no Windows event logged, but once the /heath page is reachable, then the application is ready. If you're using SQL Server and IIS on the same box, then both of those must first load before ProGet can start. Thanks, Steve

@atripp the health endpoint looks good, thanks

@forbzie22_0253 setting the proxy programmatically is not something we currently support or document at this time, but if you're dedicated you could use native API to the newly-developer settings API: https://github.com/Inedo/pgutil/blob/thousand/pgutil/Settings/ListCommand.cs It's configured via values in the Configuration table.

@atripp thanks, resolved now.

Hi @forbzie22_0253 , This refers to Delete Package, which was introduced in ProGet 2023: https://docs.inedo.com/docs/proget-api-packages-delete We don't really document/track what Native APIs change between releases, so I'm not really sure: https://docs.inedo.com/docs/proget-api-http#native-api-endpoints You can do a comparison in the /api/reference page. Thanks, Alana

@atripp thanks for confirming

Hi @forbzie22_0253 , For the Native API, you would pass in a base-64 encoded string value for byte[] values. Sorry that we don't have any examples; it's not a very friendly API, and we don't call it via JSON ourselves. Most users will configure LDAP or SAML, so so this isn't a big priority for us to document or create an API for as you can understand. If you find something that works, please do share it here :) Thanks, Alana

@forbzie22_0253 you can use the same ProGet Free on multiple instances

@atripp thanks for confirming.

Just to close this thread off. I tried below but no joy: Rebooting server several times Server is not under any load All other feed related API's worked fine Re-installed proget Resolved: Re-installed proget and re-created DB

Hi @forbzie22_0253 , We are aiming to release ProGet 2024 in early April; here are the upgrade notes in progress, which will give some idea of what's coming: https://docs.inedo.com/docs/proget-upgrade-2024 Best, Alana

@Dan_Woolf awesome thanks

So its early days but performing the basic Functions from both the PowerShellGet and PSResourceGet modules seems to work as expected without issue, i.e. Find-Module, Find-PSResource, Install-Module, Install-PSResource, Publish-Module, Publish-PSResource work well. I guess the main reason for asking this question was to check that you guys keep track of these modules released by Microsoft since they are widely used and its nice to know support is on hand if necessary. Its always comforting to know that a vendor is keeping track of issues on platforms such as GitHub etc.... thanks for prompt replies.