[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Friday 26 August 2005 9:42 pm, Thomas Arrow wrote: > After hearing how easy debian was supposed > to be this was very disheartening. It is Apache2 that is perhaps confusing you with the new config. You should create a virtual host in sites-available and symlink that file in sites-enabled. $ ls /etc/apache2/sites-available/ Example: neil@garfield:~$ cat /etc/apache2/sites-available/garfield NameVirtualHost garfield.codehelp <VirtualHost 192.168.0.1> ServerAdmin neil@xxxxxxxxxxxxxxxxx ServerName garfield DocumentRoot /home/codehelp ErrorLog /var/log/apache/codehelp/error.log <Directory /home/codehelp> Options +Includes AllowOverride FileInfo </Directory> ScriptAlias /cgi-bin/ /home/codehelp/cgi-bin/ <Directory /home/codehelp/cgi-bin> Options +ExecCGI </Directory> </VirtualHost> # ls -l /etc/apache2/sites-enabled/ 000-default -> ../sites-available/garfield Putting your files in /var/www/ or similar was always a dirty hack approach. The "right" way to do it, even with Apache1, was with virtual hosts. P.S. The thing that is easy with Debian is installing packages and their dependencies. Configuration is quite another matter. Apache2 is installed if it runs at all. If it doesn't show the files you expect then it's the configuration that needs to be tweaked and if that involves user files (as a website does), you can't really blame the installer. Some packages will install such files and ask the user where to put them or where to find them but Apache is one of those packages that will tend to require some knowledge of the configuration before it can be useful. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
Attachment:
pgpjPFTdnaKD3.pgp
Description: PGP signature