From .dev to .test for development

Like most who use Valet (and many who don’t), I’ve been using the .dev TLD for projects on my development machine. And while I mostly use Firefox as my dev browser I do sometimes use Chrome. And Chrome no longers allows .dev to be used in this way (at least not without setting up HTTPS) – and who knows, perhaps Firefox will follow suit.

But the thing is, .dev is actually a valid TLD that’s owned by Google. We probably shouldn’t have been using it like that in the first place.

As this person (and others) have said, we really should be using one of the TLDs that are reserved for such things. My first thought was that I’d use .localhost for dev work and .test for testing, but .localhost may not work with VMs.

So I’m thinking I’ll just switch Valet to use .test, both for development and for testing, unless / until someone comes up with a better idea that works with VMs and both major browsers without needing to bother with HTTPS.

PS – I’m a hobbyist developer (my day job is in IT but not as a coder) so for me it’s simply not worth the hassle to set up certificates when I can simply type valet domain test in three seconds and then get back to coding. YMMV.

Advertisements
From .dev to .test for development

The Servers, the Timezones and Me

So I’m trying to write a web-based app that tracks when something happens. You click a button, and the web app records when you clicked it.

Sounds easy, no?

The problem is timezones. I live in Australia, and the web server is in the USA. So if I click a button at 8pm (in Australia), the web server records the click at 1am (in California). Or possibly 2am or 3am in California, depending on who’s in Daylight Savings and who isn’t. Other users of my app could be in any country in any timezone in the world. Continue reading “The Servers, the Timezones and Me”

The Servers, the Timezones and Me