If I were you, I'd install apache on my own machine and set up the
configuration there.  Don't even bother installing the service, that
way you have to use the command line.  Once you get a configuration
that works the way you want, send that to your server admin.

If you need to change things between dev and production for some
reason (like you don't have the same directory structure), you won't
be able to load the production conf file on your dev machine.
However, you can run a 'configtest' command on it, and it'll check the
syntax.  Not guarenteed to be perfect, but it'll give you a pretty
high level of confidence.

cheers,
barneyb

On Fri, 10 Sep 2004 15:38:16 -0400, Rick Mason <[EMAIL PROTECTED]> wrote:
> All,
>
> Tried unsuccessfuly to complete my first Apache installation
> yesterday.  The install went fine and I could view the test page.  But
> I couldn't get it to point at my websites directory.
>
> I installed on Windows NT 4.0 (as a  service) and at present the site
> is straight HTML.  I spoke to a member of our CFUG who runs a hosting
> company last night.  He said to send him my httpd.conf file, he would
> edit it for me and send it back, which he did.
>
> Well I am not at work today but I sent it to the server tech who now
> tells me with the new file that apache won't even restart.  My friend
> sent me some commands to type into the console to test the file.
>
> But the tech says he can't type anything into either of the windows in
> the console!  If I could type into the console (from what I
> understand) apache would parse it and at least we would have an error
> message that would point us towards the problem.
>
> I would appreciate any help from any Apache gurus out there.
>
> Rick Mason
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to