params.json

{"name":"Localtest.me","body":"localtest.me\r\n================\r\n\r\nCredits: Scott Forsyth, Imar Spaanjaars, others\r\n\r\nSave this URL, memorize it, write it on a sticky note, tweet it, tell your colleagues about it! \r\n\r\nlocaltest.me (http://localtest.me)\r\n\r\nand\r\n\r\n*.localtest.me (http://something.localtest.me)\r\n\r\nIf 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.\r\n\r\nThis 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.\r\n\r\nHere’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.\r\n\r\nExamples:\r\n\r\n    http://localtest.me \r\n    http://newyork.localtest.me \r\n    http://mysite.localtest.me \r\n    http://redirecttest.localtest.me \r\n    http://sub1.sub2.sub3.localtest.me\r\n\r\nYou name it, just use any *.localtest.me URL that you dream up and it will work for testing on your local system.\r\n\r\nMore details\r\n================\r\n\r\nRead the introduction by [Scott Forsyth](http://weblogs.asp.net/owscott/archive/2012/05/14/introducing-testing-domain-localtest-me.aspx)","tagline":"localhost testing done right","google":"","note":"Don't delete this file! It's used internally to help with page regeneration."}