4 ms·
I usually just use the real sitename with a .vm tld if I'm working in local dev space. If it turns out that someone starts up a .vm tld for real, well, no loss
by drivingmenuts 12y ago
I usually just use the real sitename with a .vm tld if I'm working in local dev space.
If it turns out that someone starts up a .vm tld for real, well, no loss. I'll just switch to something else.
There's no right and no wrong way to do this on your local machine as long as you don't break the internet for everyone else and as long as it's repeatable/undoable.
- kgc 12y agoHow do you do that .vm thing?
- drivingmenuts 12y agoIn my hosts file, sites that are on my local vm are referred to as project1.vm, project2.vm and so on. Each virtual host is configured with the name project1.vm and so on and so forth. If I really felt like it, I could put a site on my called yahoo.com and change my hosts file to point that instead. I don't use yahoo for anything (nothing against them, I just don't) so it wouldn't hurt anything. Additionally, my vms all have two network addresses - one is dynamic from my router (for updates, etc.) and one is a host-only connector with a fixed IP. That's the address I use to connect to the sites. I don't bother with running a private DNS or anything - I'm more concerned with site development, not routing issues. The VM is an ends to a means and all that other stuff, while useful to know, takes up time I don't really feel like spending.