hi all, thanks for the interest/comments; I decided to write-up a page that details this on the docs.
http://inedo.com/support/documentation/proget/feeds/other-types
I'm hoping we can use this public thread to maintain the discussion on technical detail; otherwise it'll get stuck in my email, or somewhere else, and we can get everyone to chime in this way.
That said, @M-W if you've got any insight into how R/CRAN works please do share :)
Of course, plan versioning is introduced in a later version, and Rafts (which allow for Git-based storage) is coming in 6.2.
I definitely understand the hesitance to upgrade, but worth noting ---- for once 6.2 comes around we'll offer some great migration tactics to let you pull applications from really old versions of BuildMaster. We'll also better support multi-instances of BuildMaster, so each group can upgrade as they'd like.
That said, the Plans database table will contain your OtterScript plans. Not sure if that's a good solution, but pulling from that table will give you latest versions.
Hello;
There may have been a miscommunication somewhere; do you know specifically what you were told?
We recently added the Feeds Management API, but that's only to manage feeds (not packages).
I just updated the documentation, and it will be published soon.
You can delete (permanently remove) or unlist (hide from most search results) NuGet packages from your feed by navigating to the package page and clicking the corresponding Delete Package or Unlist Package button. These actions require the
Feeds_DeletePackageorFeeds_UnlistPackagepermission attribute, respectively.
To programmatically delete a package from your feed, you can use the NuGet CLI's delete command, or make a
DELETErequest via HTTP:
DELETE http://{proget-server}/nuget/{feed-name}/package/{ID}/{VERSION}`
Note that this behavior is different than NuGet.org's DELETE command, which unlists packages instead.
To programmatically unlist (or relist) a package, you can use the
NuGetPackagesV2_SetListedmethod within the Native API.
Is that helpful?
Definitely sounds like a bug; we've get it logged.
By the way, we've got some real exciting container/registry features coming very soon in ProGet 5.3. Stay tuned!
Hi @jeff-miles_5073 ,
Thanks for the first inquiry; I just updated the documentation! These must be "relatively new", and I know we've had a few customers using universal packages for this.
We have some Terraform integrations on our roadmap for 2023, so this definitely something we'll look into on our own as well.
Cheers,
Alex
Just as an update, we will be doing this:
https://inedo.myjetbrains.com/youtrack/issue/PG-1555
"Proxy npm audit requests to npmjs.org (experimental)"
Hi @shfunke_1795 , @jrottmann_6111
Thanks, I just added this to our documentation page!
I didn't look too deeply, but I found some initial documentation:
https://wiki.alpinelinux.org/wiki/Package_management
It seems this is "like Yum/RPM but for Alpine Linux"? None of us here use Alpine Linux, so there's a pretty big learning curve to get started. Any help here would be appreciated, and definitely move this along :)
Is this related to "APK" that Android uses?
Is the "API" mostly like basic file downloads, based on an index file? Are you able to "hack" or do a PoC using ProGet Asset Directories?
Hi @tkolb_7784
I wanted to provide an official answer to this:
Are there plans for (easy) HTTPS support in the internal webserver? Applying a self hosted certificate and deploying it to all build servers and developer machines seems over the top for me right now.
Yes. Not exactly sure how yet, but we would like the integrated webserver to support this as easily as possible.
@shayde @sebastian really appreciate the help, we'll get this incorporated ASAP !!
Thanks for clarifying @sebastian
So I'm not exactly thrilled by this UI, but maybe this is fine.
What do you think?
This is a kind of "quick and dirty" page that would show up if you clicked on that GPL-2.0 license and the "# projects" number.
Here's one for the packages as well:
