Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I've just followed this tutorial on setting up name-based virtulization in Apache, and it worked really well.

The tutorial basically got you to add a config file to sites-available called yourdomain.com, and then link it to sites-enabled.

By default, apache includes two site config files in sites-available, default and defualt-ssl.

Should you edit these files or remove the link form the sites-enabled directory?

After playing around with this (locally), I realised that by default the default site points to your root /var/www directory, and so if someone goes to the IP of your server directly, could they not then see all the vhosts and other directories in /var/www, unless the default vhost config is changed to point to a different directory, or remvoed from sites-enabled?

I'm just wondering what is commonly done with the default site if the server is being used for name-based virtualization?

Sorry if I got some of this incorrect as I'm quite new to running my own web server.

share|improve this question

2 Answers 2

up vote 5 down vote accepted

Just disable them if you're not using them

a2dissite default
a2dissite default-ssl
apachectl graceful

This simply removes the link to sites-enabled, so they're not included in the config anymore

share|improve this answer

You can disable the default files which is equivalent to removing the link from sites-enabled directory.

a2dissite default

If you don't want to disable default site but want to hide the directories then you can put up a home page (index.html) in /var/www/ or hide the directory indexes.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.