3 ms·
I like the clean approach, but hesitate to use my hosts file for blocking unwanted stuff on my development machine. It is 3:00 am the app breaks in production
by allendoerfer 13y ago
I like the clean approach, but hesitate to use my hosts file for blocking unwanted stuff on my development machine.
It is 3:00 am the app breaks in production while the development version magically works. You question your ability as a developer and a human being in general while blaming your browser, your os, your DNS secretly knowing in the back of your head, that that you must have done something really, really stupid. Why could you not have waited until tomorrow to push?
Finally the mixed feeling of relief and thinking you are the dumbest person in the world, when you remember your hosts file while hacking over SSH on production files, which you totally should have considered instantaneously.
I remember reading a story, where the legal department of a company in Germany sent hundreds of cease-and-desist orders to websites, which where all displaying their images. Strangely the image just appeared on company computers …
- ams6110 13y agoAs I generally just block ad sites, I haven't had any real issues using the hosts file that way. Obviously it's not a good idea to block resources needed by your app. I have had similar experiences though, where I put a dev machine ip in my host file with a production domain name, to test stuff before the name was actually live in the DNS, then later being confused about why the "live" site wasn't showing some content (duh... still pointing at the dev machine).