Update: as announced and expected, Apple has replaced DiscoveryD with mDNSResponder in 10.10.4. For those of you running 10.0.4, this article no longer applies. In case you’re stuck on 10.10.0, .1, .2 or .3, read on :)
A long long title, but accurately descriptive :P Poor English? Perhaps, but it does say what is to be said;
If you have experienced one of the following issues, then you should read on;
Your computer’s name is already in use, your computer has been renamed to iMac (2)
Your IP address is already in use (even when you’re the only one at home)
Opening a website in Safari takes “forever”
You cannot find your (other) computer on the network (even though you’re sure it’s turned on)
Lucky enough to have a Macbook Pro 17″ with an ExpressCard/34 slot? Then you’re not lucky enough to have built-in USB 3.0. We can fix that! You need to spend about 10 to 15 USD. Interested? Read on! It took me months just to find this post which gave me a 10 minute solution.
I too have been captured by “the need to get certified”. Certified Secure offers training and exams and ultimately certificates. SQL-injections, Path-traversal, Cross-Site Scripting, Cross-Server Request Forgery etc. etc. It’s a lot to learn and for me – being a developer – and for you – assuming you are one too, reading my blog – it is a necessity!
Yosemite introduces a lot of great features. I personally love Handoff where you can start a document or e-mail on one device and seamlessly continue it on a different one. I already had it working between my iPhone 5s and iPad Air but soon found that my Macbook Pro did not comply to the technical requirements.
I got it working now! If you want to know how; then read on!
[update oct 2nd, 2015]
With 10.11 El Capitan I followed the instructions to re-enable Continuity and found that my WiFi stopped working (‘No WiFi Hardware Found’). Turns out, all I needed to do was to disable kext-signing check with
While Redmond is starting their photocopiers (the age old story of how Microsoft keeps copying instead of innovating), we Mac users start our updates. OSX 10.10 Yosemite brings Apache 2.4 and PHP 5.5 to our playground, but not everyone is happy with that. Also, not all software survives the upgrade. Here is what I had to do to fix my development environment.
PHP Upgrades are a pain in the ass but from time to time, it’s desperately needed. For a hobbyist with one or two websites, it’s not that much of a deal to check your code and update, but what if you have hundreds of websites running on your servers? Automated tools would be the better choice.
Luckily there’s PHPCS – the PHP CodeSniffer – to check your code for appliance to a certain set of coding standards.
[EDIT: nov 6 2017: fixed dead link, added troubleshooting steps below]
Still not seeing the new version?
The command above should install the old PHP 5 in /usr/local/php5 (which should be user-writable) and also write a new config file in /etc/apache2/other/+php-osx.conf, so please check and see if both exist.
If you installed PHP 7.x, the folder is /usr/local/php7, of course.
Run apachectl -t -D DUMP_INCLUDES and check if the new config file is loaded (should be /etc/apache2/other/+php-osx.conf)
Try apachectl configtest and see if any errors occurred
After experimenting with Apples Server.App and removing it (for not really needing it) the built-in Apache was no longer functioning and all I could get out of it was; “Websites are turned off. An administrator can turn them on using the Server application.”
You can expect updates on all posts of the series ‘The Ultimate Development Webserver’ and ‘Handy Scripts’ where needed in the next few months (time permitting and if the beta will run stable enough inside VMWare Fusion)