Set a local domain to ease local development
If you’re a web developer you probably do a fair amount of development on your local machine using either the built-in Mac OS X Apache server or, in my case, something like MAMP. You can make your local development life a bit easier by setting a local domain, here’s how.
from the Mac Terminal type the following:
sudo nano /etc/hosts
this will bring up the /etc/hosts file in the nano editor, it will look something like this:
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
next, you’ll want to add the hostname (in this case, local.dev) you’d like to use locally to the end of that file on a new line, in the following format:
127.0.0.1 local.dev
Save the changes to /etc/hosts file by hitting Control-O and then Control-X to exit. Now you can access your local domain via the web browser, ftp, or whatever other means.
Hi Bill,
how is this different than using ‘localhost’ which is already aliased?
regards,
aitch
It’s prettier?
It also allows you to create more than one ‘site’ in conjunction with a bit of apache config twiddling. Something along the lines of:
site1.domain.whatever
site2.domain.whatever
Don’t ask me how, this is a comment, not a hint!
@Woodgie, ah, I see that. And for brevity, the alias could be shorthanded to, say, lh.d, lh.qa, and lh.p for dev, qa and production. Yeah, the apache config twiddling needs to be alluded to, at least ;-]
There is more to it than that. The main benefit is your local websites will have private sessions from one another thus preventing session overwriting when you swicth between one site and another using the same browser instance.
Does this mean I can do without MAMP?