We have moved our forum to GitHub Discussions. For questions about Phalcon v3/v4/v5 you can visit here and for Phalcon v6 here.

Installing Phalcon on Mac OSX

When you click on the download area from Phalcon's website, it shows you a tab for Linux / Unix / Mac, but don't explicitly tell you which code you should use for Mac OSX.

Also, when you try a search on Google it gives you this page but when you try to run any of the brew codes it returns error with this message:

Error: No available formula for php54-phalcon

There should be an easier guide to install Phalcon on Mac OSX, just like there is for Windows or Ubuntu, for example.



382
Accepted
answer
edited Sep '14

Did you do first tap the PHP repo?

brew tap homebrew/homebrew-php
brew install php54-phalcon

You might want to take a look at: https://github.com/Homebrew/homebrew-php

edited Sep '14

Did you do first tap the PHP repo?

brew tap homebrew/homebrew-php
brew install php54-phalcon

You might want to take a look at: https://github.com/Homebrew/homebrew-php

Thanks @melz, the brew tap worked like a charm.

However I still think there should be a note about it on the download page, just to make it easier to users which, like me, don't have all the knowledge about certain parts of the instalation process using Homebrew.



64

Hello , I wonder what I should do after installing php56-phalcon with the brew.

I have no web server on my mac, I can install nginx ?

Most Macs comes with Apache installed (depending on your version of Mac, it is either 2.2 or 2.4).

For installation notes on nginx (and other web servers), see: https://docs.phalcon.io/en/latest/reference/install.html#installation-notes



64

Melissa, thanks.

However NOT Getting set up with nginx in any way.

I wonder how to download and use version 1.3 and not 2.0.

Using brew he give me the most current version

Usually, I would just edit the formula if there was a particular version I had to stick with. The proper way would be to fork homebrew-php and then you would tap it on your local machine. But that would mean having to pull the changes to your repo all the time.... so yeah, I'd avoid maintaining different versions, etc.