Skip to content
No description or website provided.
JavaScript
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
fonts Move content across from gh-pages because Aaron told me to May 17, 2012
images
javascripts
stylesheets
CNAME
README.md Indenting May 17, 2012
STAR_localtest_me.pfx
STAR_localtest_me.zip
index.html
params.json

README.md

localtest.me

Credits: Scott Forsyth, Imar Spaanjaars, others

Save this URL, memorize it, write it on a sticky note, tweet it, tell your colleagues about it!

localtest.me (http://localtest.me)

and

*.localtest.me (http://something.localtest.me)

If you do any testing on your local system you’ve probably created hosts file entries (c:\windows\system32\drivers\etc\hosts) for different testing domains and had them point back to 127.0.0.1. This works great but it requires just a bit of extra effort.

This localtest.me trick is so obvious, so simple, and yet so powerful. I wouldn’t be surprised if there are other domain names like this out there, but I haven’t run across them yet so I just ordered the domain name localtest.me which I’ll keep available for the internet community to use.

Here’s how it works. The entire domain name localtest.me—and all wildcard entries—point to 127.0.0.1. So without any changes to your host file you can immediate start testing with a local URL.

Examples:

http://localtest.me 
http://newyork.localtest.me 
http://mysite.localtest.me 
http://redirecttest.localtest.me 
http://sub1.sub2.sub3.localtest.me

You name it, just use any *.localtest.me URL that you dream up and it will work for testing on your local system.

More details

Read the introduction by Scott Forsyth

Something went wrong with that request. Please try again.