Comments on: How To Setup Development Domains On OS X

By: Justin

Justin — Fri, 13 Feb 2009 23:10:58 +0000

It’s worth mentioning that in the default httpd.conf for Apache2 that comes with OS X 10.5, that the vhosts go in /private/etc/apache2/extra/httpd-vhosts.conf and that the include line for that file in httpd.conf needs to be uncommented. Caused me a bit of a run around looking for the issue.

By: Gabriel de Kadt · Subdomains on localhost in Mac OS X 10.5 Leopard

Gabriel de Kadt · Subdomains on localhost in Mac OS X 10.5 Leopard — Wed, 19 Nov 2008 17:39:17 +0000

[...] how-to-setup-development-domains-on-os-x/ [...]

By: Webagogue » Blog Archive » links for 2007-01-25

Webagogue » Blog Archive » links for 2007-01-25 — Mon, 19 Mar 2007 04:51:31 +0000

[...] How To Setup Development Domains On OS X at The Apple Blog (tags: osx domain development hack howto) [...]

By: Over 60 of the best resources for Web Designers « usrbingeek’s musings

Mon, 05 Mar 2007 19:29:09 +0000

[...] How To Setup Development Domains On OS X [...]

By: Chip Brown

Chip Brown — Thu, 01 Mar 2007 06:04:35 +0000

So are there any ‘gotchas’ to watch out for?

This is the kind of thing I’ve wanted to setup for months. I had no problem getting it to work at the office, but now I’m trying to set it up on my home machine with no luck.

Both are OSX 10.4 using the default install.

I’m trying to setup multiple testing domains with very erratic results, mostly 403 errors, then it will start working but pointing the wrong directory.

By: Wired For Gadgets » Blog Archive » Setup Development Domains On OS X

Wired For Gadgets » Blog Archive » Setup Development Domains On OS X — Tue, 26 Dec 2006 02:53:00 +0000

[...] How To Setup Development Domains On OS X [The Apple Blog via Digg] [...]

By: Jérôme

Jérôme — Mon, 18 Dec 2006 00:59:58 +0000

Josh,

thank you for your tutorial – although I tried the other solutions (NetInfo, Headdress) they did not really work for me. I guess I did something wrong with NetInfo and I didn’t really dug into Headress (plus I need more than just two development domains).

I don’t think doing it the manual way by editing some files is to difficult.

Again, thanks a lot, I definitely like my new shiny .dev-Domains :).

Best regards
- Jérôme

By: Icelander

Icelander — Tue, 12 Dec 2006 03:32:38 +0000

That’s good if you were the only one working on said project. If you have a team then it is pretty useless. And I hope you’re running the same PHP, Ruby, SQL version as the host you paid for or is again, useless. Is it too hard to setup a hock key in your editing app to auto-upload when you save? – Ryan Merket

If you’re working on a team, I’d hope you’d have subversion or CVS set up to check them out to your domain.

And running the same versions as your host isn’t hard. But I’ve had no trouble developing in the latest version of PHP and MySQL on a Mac and running it using an old version of both on our Linux production server.

And why would you want to auto-upload when you save? Shouldn’t you do testing first?

By: links for 2006-11-28 at BrandBrains

links for 2006-11-28 at BrandBrains — Thu, 30 Nov 2006 14:07:38 +0000

[...] How To Setup Development Domains On OS X (tags: apple mac osx development apache) [...]

By: KJ

KJ — Tue, 28 Nov 2006 16:08:01 +0000

I agree that this is a pretty good solution, but why go through the trouble? Why not just use MAMP?
For each project that I’m working on I create a seperate “htdocs” directory with a “.projectname” suffix (ex. htdocs.theappleblog). Whatever project I’m currently working on, I simply rename the folder to “htdocs”. I use this technique to manage multiple sites. Some running Movable Type, some running WordPress.
I guess the only drawback is that this is only going to work for the PHP world. Any RAILS development would have to be done through the standard Apache server or through Locomotive.