Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Message-ID: <1666.213.56.147.168.1026056282.squirrel@mail.no-log.org>
Date: Sun, 7 Jul 2002 17:38:02 +0200 (CEST)
Subject: Re: Web Server Setup on Nt 4.0 PC
From: <lolo_32@no-log.org>
To: <users@httpd.apache.org>
In-Reply-To: <lrifiu8k9md3ajg24v3i08jr79baar76lm@4ax.com>
References: <NGBBIJCJJKKBHFNELGBNAEBOCAAA.smartalarm@mindspring.com>
        <lrifiu8k9md3ajg24v3i08jr79baar76lm@4ax.com>
Importance: Normal
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

> On Sat, 06 Jul 2002 23:18:11 -0400, Bryan O'Neill, President, O & R
> Digitel wrote:
>
>>Ladies & Gentlemen,
>>
>>My goal is to transform a PII 200Mhz PC, WIN NT 4.0, into hosting my
>>webpage.  This PC is connected to a cable modem.
>>
>>Question: What do I need to do in the way of configuring this PC before
>>I install the Apache 2.0 msi file? The msi file asks for the Network
>>Domain & Server Name.  Currently, my domain, wake123.com is resident on
>>a commercial ISP server.  I'm guessing that I need to transfer my
>>webpage files to my PII PC and then by DNS(I think), register my domain
>>to point to my PC IP address.  Basically, I need a detailed process of
>>how to get this server started, using the Apache software.
>
> Bryan, are you sure you want to do this?  I took a look at your site,
> and unless you're planning a massive over-haul, your hosting cost can't
> be that much.  OTOH, if you host yourself, you are taking on an
> incredible security and reliability risk for little reward.  This is
> especially true if you use MS*, since their sense of ownership and
> permissions is kinda loosey goosey.  Apache can't protect your files
> any better than the OS does.
>
> If you are determined, though, begin here,
> http://httpd.apache.org/docs/windows.html.  Apache isn't that hard to
> set up.
>
> I don't know the details of how or what to do, but a commercial site
> needs back-up.  When your server goes down, another server needs to
> pick up the slack.  Maybe your present host can poll your server and
> redirect through his DNS to his own machines when (not if) yours goes
> down.  I'm just speculating--I have not a clue how it would be done.
>
> Sorry if I sound negative.  It's just that a business server needs to
> have a lot of TLC.  You could leave your site on the host machine and
> use your own server to develop and test improvements for your pages.
> Another use is serving up an internal site for employees (gobs of uses
> here) on your LAN.
>
> Ah, well.  The commentary is free and worth every nickel.
> --
> gt
> It ain't so much what you don't know that gets you in trouble---
> it's what you do know that ain't so.--unk
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org

I'm disagree with you, because Apache could works with an account user.
With these account, you could define NTFS permission to specify the right
access of it.
And now, Apache2 is design to work with Windows NT, 2k.
You can see http://httpd.apache.org/docs-2.0/platform/windows.html
the adress you give is for Apache 1.3


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org