If not,
here’s a guide I found simple to follow:
http://www.unixmen.com/install-lamp-with-1-command-in-ubuntu-1010-maverick-meerkat/
I also assume that you have the Apache mod_rewrite module enabled.
You can enable this by typing the following command in the terminal:
To go through this process we’re going to set up some site folders in the Document root, which for Ubuntu is located at
/var/www.
Assume in this tutorial that we are creating three sites:
mylocalsite1.com, mylocalsite2.com, and mylocalsite3.com. You can create
these through the terminal by typing:
1 | mkdir /var/www/mylocalsite1.com |
2 | mkdir /var/www/mylocalsite2.com |
3 | mkdir /var/www/mylocalsite3.com |
I have created an index.html file in each of these folders just for
testing purposes. If you already have sites in your document root you
can use those. If I open my browser to
http://localhost/mylocalsite1.com or http://localhost/mylocalsite2.com
etc I should be able to see the respective index.html pages, as you
would if you navigate to your local sites. My goal is to be able to load
my sites by just typing mylocalsite1.com, or mylocalsite2.com etc in
the browser.
So let’s set up virtual hosts. It’s actually pretty simple.
1. Add your sites to the hosts file:
In Ubuntu open your
hosts file. It should be located in the
/etc
folder. To make changes to this file you will need the proper admin
permissions, so you may need to open it as root with the editor of your
choice. I’m going to use nano:
You will have at least one line in your hosts file, maybe more. Mine looks like this:
2 | 127.0.1.1 chipmunk-thinkpadT500 |
4 | # The following lines are desirable for IPv6 capable hosts |
5 | ::1 ip6-localhost ip6-loopback |
That first line is the one that’s of interest, because it points my
local webserver (localhost) to my local IP address. I need to replicate
that so that my other sites do the same. So my hosts file will now look
like this:
2 | 127.0.1.1 chipmunk-thinkpadT500 |
3 | 127.0.0.1 mylocalsite1.com |
4 | 127.0.0.1 mylocalsite2.com |
5 | 127.0.0.1 mylocalsite3.com |
7 | # The following lines are desirable for IPv6 capable hosts |
8 | ::1 ip6-localhost ip6-loopback |
10 | ff00::0 ip6-mcastprefix |
What this basically means is that when I type mylocalsite1.com in my
browser it’s going to resolve back to my local webserver. Same with
mylocalsite2.com, etc. You can do as many of these as you want for as
many local sites as you’re developing locally.
Cool, that part is done.
2. Configure Apache
We now need to make changes to our Apache configuration so that apache knows what to do to our new sites. If you navigate to
/etc/apache2/sites-available you will see two files in there:
default, and
default-ssl.
We need to add files to correspond to our sites in this folder. We
create three new files for editing, one for each site.
Remember you need
to do this with the correct permissions so you can save the files.
From the terminal:
1 | sudo nano /etc/apache2/sites-available/mylocalsite1.com |
In this new file, type the following code, remembering to replace all
references to mylocalsite1.com with your own site name that you’re
using.
[Make sure to remove all spaces just after the < tag
and just before the > tag. These are there to prevent wordpress from
trying to process the tags 
]
2 | DocumentRoot /var/www/mylocalsite1.com |
3 | ServerName www.mylocalsite1.com |
4 | ServerAlias mylocalsite1.com |
This is the minimal set of directives that I use. We open the
virtual host tag and tell apache to listen to port 80. The DocumentRoot
directive tells apache where our site files are stored. ServerName is
the server name of our site, the url that we will use to navigate to the
site. ServerAlias is any other name or url that we may use to access
the site, the most common being excluding the www. So basically we’re
saying mylocalsite1.com is equivalent to www.mylocalsite1.com. You can
add other aliases as you see fit, but this one is the most common.
There are other directives that you can add to this file, such as error
log information, admin email etc. See more information at the link at
the end of this post.
Go ahead and create one of these files for each site.
The next step is to enable these sites.
3. Enable the sites in Apache and restart Apache
Now that we have created the files, we need to enable these sites in Apache using the
a2ensite command. In the terminal, type:
1 | sudo a2ensite mylocalsite1.com |
Again remember to change the reference to mylocalsite.com to your own site
When you hit enter, as always you’ll be prompted for a password. You
should get a message that the site is being enabled, and a prompt to
restart apache. If you have more than one site to enable, you can go
ahead and enable them all before reloading apache. Once you’re all done,
you can then restart apache to allow the configuration changes to take.
1 | /etc/init.d/apache2 reload |
Once Apache successfully restarts you’re pretty much done and ready to roll.
I am now able to go to my browser and type mylocalsite1.com and it loads just fine.
Notes:
1. If you navigate to
/etc/apache2/sites-enabled, you’ll see a
symlink to each of your sites (in terminal they just look like files,
but if you browse to the folder using your GUI file manager you’ll
notice that they are links). They are placed there by the
a2ensite command we execute in the last step.
2. If you need to remove any sites, the cleanest way in my opinion is to reverse through the steps.
- First disable them using the
a2dissite command:
1 | sudo a2dissite mylocalsite1.com |
- Then delete the mylocalsite1.com file from /etc/apache2/sites-available folder.
- Then remove the reference to mylocalsite1.com from /etc/hosts
- And finally restart the apache server
Hope someone will find this guide useful. If I have made any mistakes
or missed anything, or you have other suggestions or questions, feel
free to leave me a comment below, or just a note to say hey
More Reading:
Apache Virtual Host Documentation
a2ensite, a2dissite – enable or disable an apache2 site / virtual host
No related posts.
No hay comentarios:
Publicar un comentario