It’s my first message here I love Local and can’t wait to see it evolving, without getting too heavy and slow. In fact, for me, it is almost perfect.
I am working with many clients, trying to reproduce issues they have on my local installs. I used “Live Links” many times. The URLs expires after a while (and my clients can’t do what I need right away). Also, and more importantly, it’s slow. I subscribed to their Pro service but it’s difficult to use with Local (it starts a new tunnel for each website, and the Pro service limits you to one tunnel).
I had another idea. I bought mydomain.com. This domain (and all the subdomains) always sends requests to my IP address. There is a router there. This router sends all requests coming on :80 on my dev machine, in the local network. Of course that works with a normal http server, running on :80.
I thought it would work with Local. My Local Sites are all using that same domain I mentioned before. So one website would be a.mydomain.com, for instance. Unfortunately, those requests fall flat.
I am looking for the missing piece. I feel like I need another little server here, listing on my localhost:80 and redirecting the requests from outside my network, to the local network handled by Local. But in fact, I don’t really know. Networking is not my forte
I would love to have your help. I also think many users would love to use this solution, as it is free (except the domain cost) and would be much faster than live link (no need of a tunnel through grok).
Thanks a lot