I could go on, but this is all AAAGGGHHHHH WRONG. Now you have both installed on your workstation. Then you realise that a different project requires a different versions of that same extension, or needs PostgreSQL instead of MySQL.
Then you realise that you need some extra extensions for a certain project, so you install them.
Screwing around with Apache config just to get a single domain running seemed trivial enough, but when you have about 20 domains to manage it just seems like effort, so you end up getting something like VirtualHostX which isn’t free, or MAMP Pro which is even more expensive.
Where to buy virtualhostx how to#
Still I had the issue of how to handle virtual hosts. MAMP at least gave me a little control and avoided screwing around with a stack that my OS relied upon for certain features. Sure I can arse around with homebrew to swap stuff out, but even then it gets complicated. People always said “Duh, why don’t you use OSX’s built in ‘AMP stack, but I said I liked a little more control over versions. This for me was a massive block.įor years until a few months ago I used MAMP Pro for pretty much everything. I played with Puppet and Chef to help me with provisioning the servers themselves, but then I had to work out how I was going to run the servers locally and online. So this little web developer had to do a lot of learning. Theoretically I’ve always known how it works, and I’ve worked in projects that have had these systems, but I’ve never been put in charge of how that whole situation works out. Working at Kapture I’ve been charged with something I’ve never really had to do before: Managing a big-ass architecture of different servers that all handle different tasks.
0 kommentar(er)
