seth vidal wrote:
or, fairly simply:
You setup a web app that takes the info on what the user wants on the
box and stores it in a db. Then it returns a url encoded to retrieve a
ks.cfg from a cgi based on the info in the db.
Then for the ks you specify the location of the ks.cfg as the
aforementioned url.
That's it.
-sv
I have a script similar to this setup already (one I was thinking about
using too). It reads configs from ini files on the back end and takes
flags so users can manually change some things.
-Mike
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
