Some advice please on upgrading to Yosemite (eventually).

I am going to wait for the dust to settle with regard to Yosemite and related tools.

But here is the rub: I have been using what is now an antique Zend server for development because it seemed to be impossible to get Mac OS to support debugging/apache in one iteration or another.

So my main question is will Yosemite's apache server support php debugging? Are there goign to be any other php glitches, db API's and the like?

Is there a good url on the topic yet?

8 comments
Comment actions Permalink

Hello.
I use phpStorm with all its features xDebug and so on on yosemite on a new macbook pro, no problems at all.
Please tell me which things you are interested in or things you need help to configure.

0
Comment actions Permalink

Thanks for the quick reply.

I had seen a few posts about php-storm bogging down because of the recent java update, so I was going to hold off. Java just got upgraded and everything is still fine on Mavricks.

>> I will have to get all my sym-links added in the right place for appropriate mac-apache htdocs root and a simple paste of the x-debug config needed for phpStorm, just so I can have something to compare to.
>> I am also using https, so perhaps I need to add a self-cert in there also.
>> I am making use of zend-framework2 and doctrine, so the db depedencies for this must be met by whatever php Apple is offering. If it's all baked in, cool. Prolly is.

I kinda wish I could install on a blank box and get stuff working before jumping ship, but that's how it goes.

What I don't like is how Apple's support for an installed apache keeps changing every OS upgrade. I'd like to ditch Zend b/c they seem intent on charging $$ for their server product, and I have no particular need for them. I only install the zend server stuff b/c Apple kept changing the config/available mods every friggin release.

Upgrading to Yosemite also seems to bust zend-server.

0
Comment actions Permalink

Maybe you could create a virtual machine on mac and install there without risk?

0
Comment actions Permalink

I think a more straightforward approach would be to see if xdebug works via Mavericks, yes? That to me is the worst of it, since I used to use the installed apache anyway several OS generations ago.

I think Apple fixed the access to it.

Then I could swap over in place and ditch the zend server which requires some baby sitting anyway (it tends to seg fault if I sleep my desktop, so I stop the server before hand and have to start it manually in the morning).

0
Comment actions Permalink

Sorry, I don´t understand your problem. xDebug works for yosemite, I use it.

0
Comment actions Permalink

Because I want to work out all the kinks in Mavericks before commiting to Yosemite. If I can transfer back to the installed apache, then I also get rid zend at the same time. It is getting out of date anyway. In this way I can reasonably move forward.

Thanks for your replies!

0
Comment actions Permalink

You should really use a Vagrant/Docker box with suitable base image - preferrably closest to your production environment. Those typically come with any features you might need, including debugger. You'll be fully independent of OS quirks, will be able to reset its state instantly and more.

There is another problem with Yosemite - graphical glitches in IDE in full screen mode / on scrolling.
See https://youtrack.jetbrains.com/issue/IDEA-131632 and related

0
Comment actions Permalink

Ill echo what others are saying in that you should extract your development environment from your workstation.  I love running mine in a VM.  The benefits are numerous as to why but a couple would be:

1. Ability to mirror a particular production environment
2. Avoiding instability from upgrades on workstation
3. Portability as you are not tied to one workstation
4.  Redundancy in the ability to back up and spin off other environments

I have a little VM that is the same setup as my production server running in VMWare Fusion on my Mac.  I just use samba to share up my web directory and away I go.
A bigger deal is that you either need to run the old java 1.6 which does not run well on osx 10.10 or you need to run java 1.8 which does not run phpstorm well.


0

Please sign in to leave a comment.