At 09:21 AM 6/14/00 , you wrote:
>Hi all,
>
>Before I start 'messing' with Apache , i want some advice :
>
>What i want to do : Use my webserver as a Testing/debugging site for my
>webpages/scripts before
>they are uploaded to my Hosting Company's servers ...
>
>the Questions :
>
>a) Should i use the default /home/httpd/html/ directory , or use some
>other directory ? ( I feel reassured when i see the default
>Apache index.html :-)
>
>b) Should i use the virtual hosts option ?
>
>c) Is Samba access good enough or do i need to configure FTP access to the
>web directory suggested in a & b above ?
>
>Any other advice from people who do something similar with their Apache's
>would be most welcome !
I just set up a server like this. First, I would try to make your server
set up just like the ISP's. For example, ISP's have different policies on
where you can put CGI scripts and if your usage disagrees with their
policy, you may need to change a line or two in all your scripts. Some
scripts might not work at all (e.g., if you want a dynamic homepage but
cannot run CGI/SSI/etc in your home directory, you're screwed).
Samba will work fine if you use a DOS editor that respects UNIX file
formats. It is a recipe for frustration if you use an editor which does
not. I like ftpedit which combines a programmer's editor with an ftp
client (in fact, I'd like the same thing for Linux if anyone knows of such
a beast).
I cannot think of a way in which virtual hosting will matter.
I would make your site directory-independent. You can most easily view it
by setting up an alias in apache.
You're also going to have to resolve names some way, have you solved
this? I just use /etc/hosts on my linux machine and c:\windows\hosts on my
win95 machines.
-Alan
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
