Sorry for the complication. We put all the stuff not directly managed by Satellite/spacewalk under /var/www/html/pub/ and reference it as
http:/<satellite_fqdn>/pub/<path_to_file> That was recommended by a Red Hat employee-consultant who was engaged for the initial installation. Has worked out fine for us. On 2014-09-16 11:28, Glen Collins wrote: > Thanks all for the replies. The reason to use RPM is to be able to download > self made configuration/repo files from my Spacewalk server. The RPM will > have all the necessary files to configure the local system to be attached to > spacewalk. This just will make it simple for my enduers not having to edit > repo files not copy the RPM from their local workstation to the new system > their built. Using RPM with the HTTP functionally just makes it easier to > attach. And from that point Spacewalk will take care of the rest. > > Thanks again! > > Glen Collins > > ------------------------- > > Yes, hence my remark that you could use rpm and URLs with this setup if you > want. Was just giving a working example. > > On 2014-09-16 10:10, Thomas Foster wrote: > >> Its the same..createrepo creates the necessary files to allow yum to >> download the files from a webserver. > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list [1] Links: ------ [1] https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
