Hi @jharbison_7839 , We definitely need to update our release template documentation, but in the meantime... The "Allow all variables to be added" option allows you to freely add/edit/remove variable from the Build/Release pages, regardless of restrictions set-up by the Release Template. When it's not checked, only templated variables may be configured. This is not checked by default on new release templates, and prior to v7, there was no ability to edit variables using the template. So, checked = just like it was in v6.2 and earlier, and not checked is temlate-based editing. Alana

@atripp The links are very helpful... BM always showing the time in UTC...though I updated the server time to be localtimezone. So, the scheduling automatically changes the next run to be in the UTC format... once this is understood, I see that the cron based scheduling is working as expected... Thanks for your help.

Hi Rich, I'll try what you suggested, thank you. We tried to upgrade NPM client, unfortunately this will use also a newer version of Node.js which has a different error handling that caused all our unit tests to break. So we skipped that option until all tests are fixed. The issue appears since one year now. It disappeared for 2 or 3 months but always came back. Thanks, Jana

Hi, Please refer the below blog. You may have an idea on Semantic Versioning. https://www.meritedin.com/robust-api.html Please don't forget to take a look on the videos listed on their playlist.

@rhessinger It looks like I was on a wrong menu or something, and it thus wasn't showing up. I was able to dig around a bit and found the option though. Thanks!

I'm glad you got it working! I had forgotten that flag was even added :/ I'll chat with the docs team to get things clarified in there, or maybe see if we can change the default to enable v3 by default from now on. Thanks! -Greg

Hi @hwittenborn, Thanks for the extra information. It is very much appreciated! Are you saying the file fails to get added if you save it under the filename {feed-name}.pub? I actually used it as a gpg file extension, but honestly, your solution much better. The file extension doesn't actually matter that much. Once it is added using apt-key, it just extract to contents and stores them in their keyring. You can see this by running sudo apt-key list. I was more stating that in order for it to work for me on Ubuntu 20.04, I had to have everything named as the lowercase feed name in order for it to work for me. Although, I'm not sure if the lower case part matters. For example, for a feed name defaultdebian, I ran this: wget -qO - http://proget.localhost/debian-feeds/defaultdebian.pub | sudo apt-key add - echo "deb http://proget.localhost/ defaultdebian main" | sudo tee /etc/apt/sources.list.d/defaultdebian.list sudo apt update As a test I changed echo "deb http://proget.localhost/ defaultdebian main" | sudo tee /etc/apt/sources.list.d/defaultdebian.list to be echo "deb http://proget.localhost/ defaultdebian main" | sudo tee /etc/apt/sources.list.d/proget-defaultdebian.list and that actually wouldn't work for me. This caused a bunch of warnings when I ran sudo apt update. For some reason this only mattered in newer versions of apt though. All in all, I will update the documentation to correct your command (adding the missing '-' ) and to include the updates to the naming. Hopefully, this will be clearer going forward for other users. Thanks for all of your help! Thanks, Rich

Hi @hwittenborn, Thanks for the additional information. We talked about this in our team meeting this week and we decided we are going to clean up when restarts are needed and we are hoping to give better messaging to the user when a container needs to be restarted. Some of the restart requirements are leftover from previous requirements that have since changed. So hopefully we can make this process a bit easier in the future. Thanks, Rich

Thanks! Everything looks like it working fine.

Thanks for the update @Stephen-Schaff -- And just to add to this, you should see "Note that you can use the following alternative tags to refer to this image:..." on the browse image page.

@NanciCalo, Thank you for your prompt help! We have contacted our purchasing department to get a rush order on the new license. ("Rush" means that I hope to have it in a week or so.) I was able to put in a trial license and everything seems to be working fine. It says it is good until the 27 of June, which should be more than enough time to get a new license purchased and installed. Thank you again for keeping us running!

Hi @Ashley_8010 In nearly all of our external retail websites, there are tonnes of connections to third party websites which inevitably drive up the loading times for our customers. Some loading times can be upwards of 10+ seconds (depending on huge sneaker drops or major releases) It sounds like what might need is a sort of web bundler/packager (perhaps like webpack)? And then a Content Delivery Network on top of that, that can cache and serve static content faster than your server? We use Cloudflare ourselves. ProGet does allow you to access individual files within a package (see the files tab on InedoLib for example), and download those files with a URL like this. However, this feature was not designed to be a front-end web server, and I wouldn't recommend using it as such. Cheers, Alana

Hi @joel_6345 , Can I trouble you to read the latest version of the documentation? https://docs.inedo.com/docs/proget-feeds-nuget-symbol-and-source-server Actually I just rewrote it, so I'm really hoping that this can clarify your question .. and that it would have made it easier in the first place :) thank you

That does indeed have the info. Thank you!

Hi @atripp Unfortunately the setApiKey is not supported by the dotnet CLI. Dotnet tooling regarding package management is not ideal when it comes to nuget and dotnet nuget. Thanks for your replies.

Hi @kichikawa_2913, Sorry, this is actually expected. When we release our products, they include the extensions that were released at the time of the product release. In this case, I released this version of InedoCore after we did the product release. If you look at our documentation for upgrading your docker image, the command includes --volumes-from=proget-old. This will auto migrate the previous volumes created from the previous version of ProGet and that will keep the updated extension (as long as the previous extensions is newer than the included extension version). Also, in Administration -> Advanced Settings, you can change Extensions.ExtensionsPath to a mapped path and that will also do the same thing (if the version in this directory is newer than the included) and give you easier access to the extension files. Thanks, Rich

Looks like that was our mistake, and we missed that line in the spec. This has now been logged as PG-1964, and it will be fixed in ProGet 5.3.30, scheduled for release on May 28. Thanks for pointing it out, and sorry for the inconvenience!

@saml_4392 said in ProGet hosting in k8s or VM?: Btw, how do you measure the performance? Do you test it with a reverse proxy or use dotnet core directly? In this case, it's mostly about what happens when the servers get overwhelmed with traffic - and it's largely anecdotal. So it could just as well be related to other factors, like other programs running on the servers running the Linux clusters, or SQL Client for Linux not performing as well, or who knows. With Windows, people tend to set up dedicated or virtual servers with strict hardware provisioning.

@joshy-mathew_7277 what type of package is this? HTTP is not a great protocol for pushing really large files like that, and things like IIS and Middleware breakdown with huge requests. ProGet doesn't have any limits per se, but the 503 error means that something between ProGet and your browser is killing the request. It's usually IIS. Most of the client tools (NuGet, etc.) do not support "chunked" file uploads (Docker does), which is why we recommend using drop folder for these large files.