I have to install the 'repository' into Yum, using an RPM, and THEN I can use Yum with that repository definition to go back over the Interwebs to download the actual RPMs.
But what if my server is in a closed, locked down environment? It's not going to have permission to be able to reach out to a repository on the public Interwebs to pull those RPMs down on 80 or 443.
Any other piece of software I'd just pull the few RPMs I need, and deploy them how I see fit. Copy them onto the closed server which needs them, and deploy them manually, or push them with a remote deployment tool.
OK, so I can play with the manual installation method instead, but really why can't I just have directory listings open on the repository, and none of this amazon signature nonsense, and just download the RPMs?
I have to install the 'repository' into Yum, using an RPM, and THEN I can use Yum with that repository definition to go back over the Interwebs to download the actual RPMs.
But what if my server is in a closed, locked down environment? It's not going to have permission to be able to reach out to a repository on the public Interwebs to pull those RPMs down on 80 or 443.
Any other piece of software I'd just pull the few RPMs I need, and deploy them how I see fit. Copy them onto the closed server which needs them, and deploy them manually, or push them with a remote deployment tool.
OK, so I can play with the manual installation method instead, but really why can't I just have directory listings open on the repository, and none of this amazon signature nonsense, and just download the RPMs?