comment on

I agree with what Masem said, but I'd create one config file per virtual domain or virtual host. That way if you move one domain to another host, it is easy to move its config file rather than editing a big one. I agree that XML is the way to go, both for readability and for maintainability. Something like the following might be a start:

<config vhost="my.virtual.hostname">
  <script name="some_script.pl">
    <logfile name="/wherever/some_log" />
    etc
  </script>
  <script name="another_script.pl">
  etc
  </script>
</config>
[download]

Check CPAN for some modules that help you parse XML. I especially like XML::Simple for config files.
HTH, --traveler

In reply to Re: Running Perl scripts from a single CGI-BIN, on a multiple-virtual hosting server by traveler
in thread Running Perl scripts from a single CGI-BIN, on a multiple-virtual hosting server by ajt

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks