pow

I'm still seething about `.dev`. For those not in the know, Google lobbied ICANN to get the name and in their application they stated (repeatedly) that the intent was to buy it so that it could be reserved; as .dev was already used by developers and if someone bought it for commercial purposes it would harm the developer community.[0] .... they then proceeded to start selling them. Leading to all kinds of issues, the exact issues that they raised... https://github.com/basecamp/pow/issues/397 https://github.com/laravel/valet/issues/433 https://danielbachhuber.com/switch-laravel-valet-from-dev-to... https://community.localwp.com/t/dev-domain-doesnt-work/4277 https://forums.theregister.com/forum/all/2017/11/29/google_d... [0]: https://gtldresult.icann.org/applicationstatus/applicationde...

I think about a decade ago pow did something similar, but using the .test domain, and perhaps ruby specific https://github.com/basecamp/pow/tree/master

https://github.com/basecamp/pow Pow used .dev and .test in the 2000s-2010s

I don't think IANA explicitly reserved .dev. It was made popular as a local dev domain by Basecamp's Pow[1] and Laravel Valet[2]. IANA only defines .test, .example, .invalid, .local, and .localhost as reserved (with .onion being the latest addition in 2015[3]) Though in this list, only .test and .example are marked as non-special and must be resolved normally by RFC 6761, and .local is reserved for mDNS by RFC 6762. In this list, .test would have been the most appropriate for Pow to use. CydeWeys (Tech Lead of Google Registry) has commented on HN in the past that they did not anticipated people weren't following the best practices[4], which makes me think IANA should have given .dev the same treatment as .onion: by explicitly reserving them (but this is another topic to discuss). [1]: https://github.com/basecamp/pow [2]: https://github.co

Basecamp’s Pow project comes to mind. It enables zero config local development configuration, whereby at the time it would make your locally running dev server available on .dev So instead of having to spin up a local server and then visiting say 127.0.0.1:3000, I could instead just visit myappname.dev and it would show me what would previously show on localhost or it would spin up a server first for that app then show it to me. They switched to .test in response to google’s change. Official site: https://pow.cx Thread on change from .dev to .test https://github.com/basecamp/pow/issues/386

Let's hope this issue gets some traction: https://github.com/basecamp/pow/issues/545 It's a bit unnerving that the project hasn't seen an update since 2014, and has 100 open issues.

Pow has a special support for .xip.io domain[1]. If you add `export POW_EXT_DOMAINS=10.0.0.1.nip.io pow` to `~/.powconfig` it should work[2]. I haven't tried this myself though. [1]: https://github.com/basecamp/pow/blob/master/lib/configuratio... [2]: http://pow.cx/docs/configuration.html

Does that actually work? On my machine pow has ipfw configured so that it only forwards requests to 127.0.0.1 not to 10.0.1.whatever so project.10.0.0.5.xip.io fails. Filed an issue: https://github.com/37signals/pow/issues/293 Edit: a) I should RTF man page for ipfw, b) nevertheless my OS X behaved strangely. I rebooted and now everything works. Anyway, great project, have been a happy user of pow master for quite a while.

New in this version: improved installation and uninstallation scripts, better error pages when things go wrong, support for default virtual hosts, and support for Rack application reloading with tmp/always_restart.txt. See the full changelog here: http://pow.cx/manual#section_6 This version is also compatible with Showoff (http://showoff.io/): http://pow.cx/manual#section_4 Install or upgrade: curl get.pow.cx | sh And let's just go ahead and get this out of the way now... Pow 0.3.0 is fully tinfoil-hat compliant. If you are averse to installing things the easy way using curl, feel free to build Node yourself and install Pow with npm: https://github.com/37signals/pow/wiki/Installation#installin...

If you want https you can install from github: curl https://github.com/37signals/pow/raw/master/install.sh | sh

pow isn't written in ruby, but javascript. So it might be installable from npm soon. If you `git clone git://github.com/37signals/pow.git`, you can install it from source with `npm install -g` (requires npm 1.0)