Will very likely work without having to wget it first:
rpm -ihv http://<ProGetServer>/endpoints/RPMTest/content/apacheds-2.0.0.AM25-x86_64.rpm

On Centos/RHEL/Fedora the easiest way to setup a rpm repo is to just place all rpm files on a file server and run createrepo . from the top level directory to create all the meta.

And update your /etc/yum.repo.d/fedora.repo file to point at your file server.

It would be useful to see Proget support rpm version management as well as pacman version management.

I could test something... Let me know.

@apxltd After re-reading my post I think I was a bit harsh, sorry. Proget really is a great tool and I love what Inedo has done with it up to this point. The documentation is quite good as I've referenced it quite a few times and found it helpful. Just found to be lacking where I had got stuck (and my frustration got the best of me). I shouldn't complain as it's trial option is free with heavy hitting features; Enough to really test it out. I'll make a note to create a page on how to set this up on a Linux box when I have some downtime.
Thanks!

Thanks Matt,

Really hope Proget creates better documentation around setting up Proget with a nginx proxy in front of it (the current documentation is pretty useless). I've wasted an entire evening trying to figure this out. I almost gave up and went back to using Nexus3.

Matts fix where he went to 'Settings > Advanced Settings' and set the 'Web.BaseUrl' to your Proget URL e.g https://registry.example.com worked fro me.

I was able to get it working nicely with this proxy in front of it.
https://github.com/evertramos/docker-compose-letsencrypt-nginx-proxy-companion

Along with Jenkins, and my other dev tooling services.

Regards,

Mark