Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Puma-dev blocking access to production level .dev domains #194

Open
leesheppard opened this issue Apr 19, 2019 · 1 comment

Comments

Projects
None yet
1 participant
@leesheppard
Copy link

commented Apr 19, 2019

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.

@leesheppard

This comment has been minimized.

Copy link
Author

commented Apr 19, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.