Hi @aneequaye_1868, I apologize, I was speaking from the mapped folder on the Docker host. Inside the container, it is still /var/proget/packages. Does this still happen on the latest version of ProGet? We did make some changes to how the headers are returned in the latest version, especially for feeds that require authentication. Thanks, Rich

Hello, please review License Key Activation Docs, especially the note at top talking about Automatic License Activation Not Working in older versions. Also... please upgrade. ProGet 5.3 is great!!

Hi @atillio-menegoni_1334, If you navigate to that artifact version in the UI and verify that cdd-application-5.7.0.5.zip exists in the list of files? If it does, can you click the file and see if it downloads manually for you? Thanks, Rich

This isn't currently supported, but something we can consider adding if you're open to using our Feature Request Process. One thing that would go a long way in helping us understand the usecase (and way to explain it to users) is suggesting where precisely we should document this, and how. https://docs.inedo.com/docs/proget/reference/api/asset-directories-api (source)

Thank you. this situation seems to be sorted in 5.3.15.

Hi @srbauti_9412, The best solution to this would be to create a new NuGet feed that uses a self-connector to connect back to your existing NuGet feeds. You can then use the connector filters to handle filtering by your package name format. Thanks, Rich

Hi @rhessinger, thank you for your quick answer. Works fine for me! Thanks and best regards, Philipp

Hi @toni-wenzel_6045, Currently, the only way to set the description would be to do it using the UI or the Native API. In order to set it using the Native API, you would need to do the following: First, Get the Docker Repository ID by making a GET request to <Base URL>/api/json/DockerImages_GetRepositoryByName?key=<API Key>&Feed_Id=<Feed_ID>&Repository_Name=<Repository Name> This will return a list of images (should only be 1 in the list) and you will need to get the DockerRepository_Id from each item. Then, you will need to POST a JSON object to <Base URL>/api/json/DockerImages_CreateOrUpdateRepository. The JSON object you would post would be: { "API_Key" : "<API Key>", "Feed_Id": "<Feed Id>", "DockerRepository_Id": "<ID from previous request>", "Repository_Name": "<Repository Name>", "RepositoryIcon_Url": "<Icon_URL>", "ShortDescription_Text": "<Short Description>", "FullDescription_Text": "<Full description (Readme.md)>" } Please note that you will need to populate all of the values. For example, if you do not populate the RepositoryIcon_Url, the value will be cleared. Thanks, Rich

Hi @nicolas-morissette_6285, No problem! If you are still having issues after you reach out, please feel free to reply back to this topic. Thanks, Rich

This is unfortunately a documentation issue. We changed some of the environment variable names for ProGet 5.3 - so you'll need to use: -e PROGET_DATABASE="Data Source=proget-sql; Initial Catalog=ProGet; User ID=sa;Password=<Secret>" \ -e PROGET_DB_TYPE=SqlServer instead of -e SQL_CONNECTION_STRING=... We'll update the docs to note this for ProGet 5.2.

@rhessinger : Thanks, tested Version proget.inedo.com/productimages/inedo/progetmono:5.3.13 and it is working now as expected.

Thanks everyone for the help. -marc

No problem, ask away :) You could. Not sure what the use case would be... But, the URLs for NuGet package versions are quite predictable, and you can discover them from the Download button in the UI. For example, the download URL for InedoLib v950.0.7 just looks like https://proget.inedo.com/nuget/NuGetLibraries/package/InedoLib/950.0.7 The NuGet API does not support Bearer authentication. You can specify an API key when publishing packages (X-NUGET-APIKEY header), and it might work when downloading packages? Haven't tested, and no one asked before. But you could also specify api:<apikey> as the basic auth credentials as well, so I guess that's really easy too.

Hi @viceice, That error is safe to ignore. It is currently a known bug and we are looking to fix that in an upcoming version of ProGet. The ticket tracking the fix for the log message is PG-1841. Long story short, the ProGet service correctly detected that the product wasn't activated, and then logged that message. But it was doing it every time it accessed license information, which is on every connector health check, replication run, etc. Activation happens automatically as soon as someone visits the Web application, and re-activation is required after upgrading certain versions. Thanks, Rich

You're welcome

Just following up- all of these issues should be resolved in ProGet 5.3.13, which will be released later today.

Hello, this has finally been scheduled for 5.3.13, which is shipping tomorrow. It addresses only this specific test case, so please let us know if you're spotting other errors.

Hi Phillipe, I created an issue on GitHub, #8, to track adding this to the extension. I'll reply back once there is a CI version released of the extension. Thanks, Rich

Hi @nuno-guerreiro-rosa_9280, No problem! Gald it helped! Thanks, Rich

Hi @barnaby-williams_8489, This is just a manual copy of the files. Thanks, Rich