[quote="A_Hull"][quote="mikeyrb"]I don't understand how we could keep the config in the database. There are likely people with different setups that require multiple configs, so you can't really store it there for all cases. Hence, which one do you choose? I say you don't. Leave it in a file, as that's the most network efficient (despite it being really small anyway).
Well if audit.vbs looks to a URL for its config, then we just have dynamically created pages for each site we want to audit.
We have a "set up site or machine" page which creates a config for a particular site or machine... obviously and stores it in the databse, then we call audit.vbs (or create it dynamically pre-programmed with its config URL)
So for example we want to audit aberdeen we use
[url]https://openauditserver/openaudit/script_config_url.php?config=aberdeen[/url]
to audit Perth
[url]https://openauditserver/openaudit/script_config_url.php?config=perth[/url]
Which throws us a preconfigured audit.vbs...
And so forth.
AND/OR we add a config paramater to audit.vbs
cscript audit.vbs config=aberdeen
or
cscript audit.vbs config=perth
I hope this makes sense....
That's what i was talking about!
Thing is, i think all these options make sense.
And this implementation doesn't include much work on the audit.vbs code, it's a matter or defining a actions queue. First it waits for comamnd line optoins then it tries to read a .config file on the same folder it's been run. The command line options could have two ways, point it to the location of the audit.config or make him fetch it remotly at the server url.
This is an example.
|