On 1/8/99 1:38 PM Mitch Vincent ([EMAIL PROTECTED]) wrote:
>Well, that's all good but my access logs and the directories I would need
>the output in are different..
This can all be sorted out if you keep track of which things are needed
when Analog is running and which things are needed by the web browser
when it is vieving the report. domains.tab and the lang directory are
needed by Analog when it is running. You can leave Analog in a single
place and run all of the configurations from there so that isn't really a
problem.
The images directory needs to be accessable by the browser. You can put
that anywhere you want on your server (one single place) and then set the
IMAGEDIR config parameter to that place for all of your configurations.
Then the reports can appear anywhere you want and will still be able to
access the graphics. Alternatively you can just make symbolic links to
images in each of the places you are writing reports, that is more work
but gives cleaner internal URLs inside the reports.
Jason
>-----Original Message-----
>From: Jason Linhart <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
>Date: Friday, January 08, 1999 1:38 PM
>Subject: Re: [analog-help] Hello Again..
>
>
>>On 1/8/99 11:39 AM Mitch Vincent ([EMAIL PROTECTED]) wrote:
>>
>>> Is there any way to use analog with more than one domain *without* having
>>>to re-compile and copy bunches of stuff to every directory? Even with the
>>>config files it looks like you have to copy the lang and images where ever
>>>you have your other domain info because you can't use absolute paths in
>the
>>>analhead.h or the config file. **And** you can't specify other paths to
>the
>>>httpdir without a re-compile... This has gone beyond the point of
>>>frustration.
>>
>>HTTPDIR is not supported in configuration files. All you need to do is
>>spell out the full path name in the configuration file. The use of
>>HTTPDIR is just a C programing short hand to avoid repeating the path.
>>
>>To support multipule domains just set the filtering and report
>>destination locations in each configuration file (one per domain) and run
>>analog several times, once for each domain. The reports can have
>>different names and all share the same lang etc. files.
>>
>>There is no need to recompile, everything can be set in the configuration
>>file.
>>
>>Analog isn't the simplest program to configure but the configuration
>>comands are all well documented. It would be much simpler if you worked
>>from the documentation instead of the analhead.h file.
-----------------
[EMAIL PROTECTED]
-----------------
Dr. Seuss books . . . can be read and enjoyed on several levels. For
example, 'One Fish Two Fish, Red Fish Blue Fish' can be deconstructed
as a searing indictment of the narrow-minded binary counting system.
-- Peter van der Linden, Expert C Programming, Deep C Secrets
--------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
--------------------------------------------------------------------
