In this case, your best bet would be the backup the database, and then only the package files of that feed. In case of DR, your other feeds wouldn't really work (no package files), but your other configuraitn (usernames, etc) would remain.

Keep in mind that Timeout (or cancellation in general) is not guaranteed, and requires that the task (generally, an operation) properly check for a cancellation token. For example, an operation that simply did a Thread.Sleep for 1000 seconds could not be timed out after 10 seconds. In a case of a stuck execution, restarting the service is the best way to clear things. So, we'd need more context to identify if it's a bug in the operation, or simply something that isn't support.

Thanks for the suggestion, it's handy to know that's possible (with a bit of scripting to move packages into the top level directory). It also seems to work pretty well running the Feed Cleanup under 4.7.14 and then upgrading.

Both of these package types will be supported in 5.2. PyPI support has now been added and published as a pre-release version of 5.2.0. Visit the ProGet Versions page to download, or get it from the Inedo Hub download.

PyPI support has now been added and published as a pre-release version of 5.2.0. Visit the ProGet Versions page to download, or get it from the Inedo Hub download.

PyPI support has been added and published as a pre-release version of 5.2.0. Visit the ProGet Versions page to download, or get it from the Inedo Hub download.

On version 5.1.17 this setting is called Web.BaseUrl

Upgrading to v5 seems to have fixed this

There was an issue (PG-1208) with semantic version-enabled NuGet feeds and retention policies fixed in v5.0.8 - an upgrade should resolve this.

Here are the features by edition: https://inedo.com/support/documentation/proget/administration/license ProGet Free is allowed for companies, however that edition only receives "community support" (i.e. this forum).

Maybe some kind of checkbox in existing UserNamePassword would be a good solution? For example, a checkbox that clearly indicates that these credentials can only be used in PowerShell?

Yes, that is OK, the differences for each edition are outlined here: https://inedo.com/support/documentation/proget/administration/license

Thanks Alana, once I installed the certificate into my 'Trusted Root Certification Authorities' and restarted the docker daemon on my client machine, things are working nicely. Thanks again for your help!

Unfortunately the Native API is essentially a database wrapper, and one of the few things that can't be handled at the database layer is encryption. While we want to create a resource credential API at some point, in the meantime, the only workaround would be to encrypt/decrypt the secrets yourself, using the Encryption Key stored in your configuration file.

Hello Alana I agree. I know that one server should be assign to a single Environment. I already use Role for the Applications (One Role = One Application), but I cannot have 1 or more server per environment as our dev team and test team like to have plenty of environment so I need to consolidate multiple environment to one server. I am already using BuildMaster (with many Pipeline Stage) to deploy to a single server the environment I want. It was a request to improve Otter which already good to make my work more simple. I understand it might not be very simple to do it. Thank you for the reply Best regards Philippe

The SQL server and the application are both on server 'Production' and the application is successfully retrieving data from the SQL server. The connection string used in the application configuration is the same connection string being used in the SQL connection in Buildmaster. It is using a SQL account, so not integrated. Here is a redacted connection string: - Data Source=*************;Initial Catalog=*************;User Id=*************;Password=*************;MultipleActiveResultSets=true;

You got it working though :)

After doing the steps in the links, I was able to remove and re-install proget (using offline installer). After that, Hub still didn't work, so I tried running the online-installer which downloads the Hub at the beginning of the install and that seemed to fix the Hub. Thanks for your help Dean.

The groupName refers to the package's group name, and it's optional. A universal package is identified by group + name + version. The files do need to be artifacts; that's what will be zipped up and sent to ProGet.