4 ms·

Do developers often run things on localhost? I mean sure, you'll have things running on your dev machine, but for me at least, http://127.0.0.1/ http://127.0.0

Do developers often run things on localhost? I mean sure, you'll have things running on your dev machine, but for me at least, http://127.0.0.1/ http://127.0.0.1/ will just show the default webroot, with its placeholder index.html. All my actual sites listen for custom hostnames (since otherwise you only get one site per machine or have to do silly things with port numbers on the url). So unless somebody has crafted a page specifically targeting me and my naming convention for local sites, this wouldn't be an issue. And of course, once you hit a site, you'd still need to deal with the same security that the public facing version sees. You certainly wouldn't go out of your way to disable that on your local machine. Databases are named, and often live within named database server instances, so they'd need to be specifically targeted as well. And, again, they have authorization to deal with. It's not like you'd leave that open either. Is it common to do it any other way?

hatsix 10y ago
Yes, When you're generally running one application server, and your other services all use specific ports by default, it's VERY common. In fact, I've not worked at a company (in 12 years of web-app dev) that used different domain names on dev machines until very recently, when it became a requirement of the software itself to have subdomain-per-client code.
flukus 10y ago
Yes, I've always run everything on localhost and use different ports, I think most devs are the same. I've never even thought of doing anything else > All my actual sites listen for custom hostnames (since otherwise you only get one site per machine or have to do silly things with port numbers on the url). It's not just web servers though, every from databases to caches servers. >Databases are named, and often live within named database server instances, so they'd need to be specifically targeted as well I think most would stick with the defaults. With mssql server it's "." or "sqlexpress" or whatever. >And, again, they have authorization to deal with. I've always used windows authentication, but that now seems like a terrible idea.

hatsix 10y ago

Yes, When you're generally running one application server, and your other services all use specific ports by default, it's VERY common. In fact, I've not worked at a company (in 12 years of web-app dev) that used different domain names on dev machines until very recently, when it became a requirement of the software itself to have subdomain-per-client code.

flukus 10y ago

Yes, I've always run everything on localhost and use different ports, I think most devs are the same. I've never even thought of doing anything else > All my actual sites listen for custom hostnames (since otherwise you only get one site per machine or have to do silly things with port numbers on the url). It's not just web servers though, every from databases to caches servers. >Databases are named, and often live within named database server instances, so they'd need to be specifically targeted as well I think most would stick with the defaults. With mssql server it's "." or "sqlexpress" or whatever. >And, again, they have authorization to deal with. I've always used windows authentication, but that now seems like a terrible idea.