Level 122
posted at the weekend, bumped for the work week crowd
Jun 22, 2019
8
Level 122
Develop on Windows 10, but not when offline
At home, I'm happy developing on Mac
On the road, I have Windows 10 laptop. I have created a development environment using WSL, mostly following the steps here https://medium.com/jackabox/setting-up-wsl-on-windows-10-to-develop-with-php-laravel-60574a8612fd
So I have Ubuntu, Acrylic DNS and Valet all working to serve sites under a .test domain
All works well, except that if I'm off-line (no wifi, or in airplane mode) then its not possible to connect to my local sites. Anyone have any suggestions?
Confusingly, curl from the command line gets the site's home page so DNS is resolved and the web server is running. Its only Chrome and Edge that refuse to connect.
Level 2
Hi @snapey,
I´ve also noticed this error. I think thats a general problem within chrome and mozilla. Look at your proxy-settings within your desired browser and in windows, perhaps there is a proxy which should be called, but can not reached so your browser can not connect to the "internet".
Please tell me about it, if this works!
Best regards,
Robert
Level 75
Another idea of course you want Linux but you could always slap on a bitnami wampstack. I just think they have the best stacks.
https://bitnami.com/stack/wamp
I know that idea is so far out in left field but I've always loved their stacks.
Level 35
Another alternative that you can look into is Laragon. I've been enjoying it since this February .
1 like
Level 67
@snapey Are you using that Acrylic thing? I was just reading that article and seeing the stuff at the very bottom about it.
We use Homestead for our Mac/Windows/Linux devs. I know that doesn't suffer from this issue.
Level 8
It's been a few years since I last used Acrylic and one of the reasons for it was exactly this. It would not work if you weren't connected to the internet, given that it works by setting the DNS resolver address of the active connection. Even if you try fooling it with a loopback interface, it wouldn't work. Not sure if that's still the case, but something to consider.
If this is the case, the only other option is to go from a virtual environment (docker, vagrant, etc.), since those do create actual networks that you can set the resolver on. It's that or just edit your windows hosts file to point whatever domain you're working on to 127.0.0.1
Level 122
Thanks for all the input guys. In the end I just went with editing my hosts file. Bit of a pain, but I don't spin up new projects every day.
Please or to participate in this conversation.