Mavericks and Apache/MySQL

I finally upgraded my office machine to OS X Mavericks, and as a result had to reconfigure both Apache and MySQL.

This post covers most of the relevant info for dealing with Apache: remapping your default web directory, enabling PHP. This post deals with setting index.php as a default document if a directory is requested.

MySQL was a bit trickier. I had installed it using Homebrew, so I had to uninstall MySQL, upgrade Homebrew, and then reinstall MySQL.

One random note: Launchbar’s ClipMerge feature stopped working, and it turns out that was because Mavericks resets the Accessibility options. I had to go to System Preferences > Security & Privacy > Accessibility and allow Launchbar to control my computer.

Using Adobe Edge Inspect with Local Virtual Hosts

At Bluecadet we like to review responsive prototypes and site builds using real devices. One of the tools we use is Adobe Edge Inspect, and it’s always worked well for previewing sites on public URLs. We happen to do a lot of development on our local machines, however, and we’ve never been able to load those via Edge Inspect. Despite the cryptic “Localhost Support” in the product bullet points, we couldn’t find much documentation out there on how to actually do that.

This blog post is old (it still refers to Edge Inspect as “Shadow”) but proved to be extremely helpful. The missing piece turned out to be, which allows you to map an IP address to a domain name. That domain name gets added as a ServerAlias entry in my Apache virtual hosts config:

    <VirtualHost *:80>
        DocumentRoot "/Users/bcideveloper/Sites/localproject"
        ServerName localproject.local
        ServerAlias localproject.*

So now when I browse using Chrome to the url the connected devices can load the site running off my local server, provided all the devices are connected to the same local network.

Prototyping Your Workflow Links

Update (2014-06-10): Jon Yablonski has put together a fantastic resource at Web Design Field Manual.

In my recent article for A List Apart, “Prototyping Your Workflow”, I wrote:

There’s a seductive danger present whenever you see someone else outline their way of working, however. It’s easy to take their process as a rigid, universal truth. The trouble is, you and your team aren’t like everyone else—you have different strengths and weaknesses. Borrowing someone else’s process wholesale ignores the fact that it probably took them lots of fumbling to get to that point, and it’s going to take plenty of experimentation on your team’s part to figure out what works for you.

That wasn’t written to dismiss what people are sharing. Quite the opposite—you absolutely should be paying attention to how people are approaching their process, because it’s near-impossible to come up with something that works well all by yourself. So in that spirit, here’s a number of links to pieces that I keep returning to when I think about process. Some are philosophical, some are technical, but they’ve all helped me in some way:

Each of those people above didn’t have to take the time to write and share about how they’re approaching their process, but they did, and I’m so very grateful for their generosity. If you’re writing about this stuff, or have your own favorite links/touchstones, please share them with our community—the more we talk openly about these things, the more we’ll be able to help our clients and ourselves.