Doing a standard install of FoundationPress on top of a WP (4.7.3) / PHP (7.0.3) / Apache / MySQL (5.5.49) non-multi-site runs fine if I go directly to e.g. foundation.dev but anything related to BrowserSync, which opens up a localhost:3000 despite setting the URL to foundationpress.dev, runs very slow. It takes 5-10 seconds to reflect an update.
Has anyone else run into this issue and found a solution? I’m not sure how the localhost:3000 wrapper conflicts with the local .dev instance but it doesn’t jive well.
After tearing the little hair left out of my skull for 3 days and trying everything from adjusting DNS settings in OSX to praying to the /etc/host gods, I found the Local by Flywheel program assigns an IP to the local server name but the long hanging is in some way (from what I’ve researched) related potentially to IPV6. I didn’t make any adjustments to my network settings, but it doesn’t like it I suppose.
So, while this works out of the box as far as accessing foundationpress.dev in my /etc/hosts file:
192.168.75.100 foundationpress.dev #Local Site
it takes a long time to work properly using FoundationPress’ npm run watch command which ultimately creates a localhost:3000 setup. To fix, I had to manually add this after “## Local by Flywheel - End ##”:
I’m sure in some cases, running this may help, which flushes the DNS cache after making changes to the hosts file: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder;
Now I can stop crying myself to sleep and start developing again.
Hey thats great news! This is related to my earlier question about the remote host issue I had. I noticed that without this extra ::1 line for each domain - when running HMR or gulp to inject changes right away - the reload is EXTREMELY slow. Thankfully this solves both issues. Excited for the next update - its an amazing piece of software. Do you by chance know when it will be released?