Re:Change http://localhost:3000 to myapp.dev with marathon-dns
by brandon_wirtz on Sunday May 05, 2013 @03:54PM
(#5659522)
I do this with Squid, or Fiddler depending on platform.
I have done a similar trick for the entire lan by doing port forwarding on DD-WRT and similar.
I pretty routinely highjack ports as domains for doing local testing. If I want to make sure that I'm hitting my own cached version of an API that I need to consume from a third party I just serve it from local. That way I can dev offline, or guarantee that I will always get the same response, or a much faster response. I could Mock it, or do a number of other things, but it is often nice to be able to see what is going over the wire, and using a proxy to handle the redirect and port change is one of the best ways to do so.
Re:Change http://localhost:3000 to myapp.dev with marathon-dns
by davewasmer on Sunday May 05, 2013 @03:57PM
(#5659531)
It's a combination of a proxy, a DNS server, a ipfw rule, and a resolver file. All that is needed to allow you to capture port 80 traffic without running your application server with sudo every time.
I have done a similar trick for the entire lan by doing port forwarding on DD-WRT and similar.
I pretty routinely highjack ports as domains for doing local testing. If I want to make sure that I'm hitting my own cached version of an API that I need to consume from a third party I just serve it from local. That way I can dev offline, or guarantee that I will always get the same response, or a much faster response. I could Mock it, or do a number of other things, but it is often nice to be able to see what is going over the wire, and using a proxy to handle the redirect and port change is one of the best ways to do so.
EDIT: Oops. Didn't notice the port number part.