Puma-dev blocking access to production level .dev domains

Question

Puma-dev blocking access to production level .dev domains

leesheppard opened this issue 5 years ago · comments

Now that Google has released the .dev domain it seems that previously used puma-dev settings now prevent the loading of websites with the TLD extension. Flutter for example will not load if you have puma-dev installed with the .dev setting: https://flutter.dev/

I removed etc/resolver/dev and the page loads. But using the .test option with puma-dev does not appear to work locally. It is installed in that directory though.

Lee Sheppard · Answer 1 · Fri Apr 19 2019 23:14:41 GMT+0800 (China Standard Time)

Just found the article about binding to a new domain.

https://www.dunkman.me/blog/2017/replacing-pow-with-puma-dev.html

In short, you can run $ puma-dev -install -d test where test is the extension name you want to use to load local env tests. Then running $ puma-dev link in each app directory to link to the new name.

Mark Madsen · Answer 2 · Fri Jul 19 2019 00:59:36 GMT+0800 (China Standard Time)

Don't use .test if you have apps with subdomains. Something bad happens to the cookies needed for authentication.

Alex Levine · Answer 3 · Mon Aug 26 2019 06:49:22 GMT+0800 (China Standard Time)

To work around it, I've been doing this on OSX.

Seems to be undone on restart fyi

# commenting out the contents of this file
sudo nano /etc/resolver/dev
# restarting the mac osx dns service (I think)
sudo killall -HUP mDNSResponder

Alan Norton · Answer 4 · Tue Mar 03 2020 00:02:33 GMT+0800 (China Standard Time)

puma-dev has moved to a default TLD of .test for the time being, but that can be overridden with the -d flag. Now that .dev is an official TLD, puma-dev doesn't want to be in the business of owning it.