You can also download Get Backup Pro 3.4.17 Article ID = 185Īrticle Title = How To Obtain/Download macOS Server for macOS 10.13 High Sierraĭetails of how to obtain/download macOS 10.13 High Sierra Server aka macOS Server 5.4-5.6.3 How To Obtain/Purchase/Download macOS Server for macOS 10.13 High Sierra WARNING: As of September 2018 Apple has gutted macOS Server and removed most/all of the useful Server features!
(Note the emphasis on whenever: adding the Server-specific configuration lines to the main php.ini file brings them into play for all use of PHP on the machine.Download macOS Server 5.9 free latest version offline setup for macOS by clicking the below button.
This will ensure that whenever PHP is fired up, it includes the custom configuration which you have set up for macOS Server. If you’re already committed to Sierra, then one solution, for now, is to append the contents of any additional custom configuration files contained in the /Library/Server/Web/Config/php directory to the end of the main php.ini file which lives in /etc. Since this can only be configured via -with-config-file-scan-dir when PHP is compiled, we cannot change this behaviour without replacing the whole kit and kaboodle. However, not having tested that solution extensively on a live server, I can’t offer any comment on whether it’s a good idea.Īlternatively, if the machine is already running Sierra, then the good news is that the newer versions match up with what is available in Sierra’s PHP 5.6, but the bad news is that PHP has not been compiled to scan the /Library/Server/Web/Config/php directory at all! So whatever custom configurations might be requird by the Server app, and whatever custom configurations you might have added to the directory on your own, are simply ignored. In principle, we could roll back to the previous version of these two lines and then drop the older modules directly into the macOS Server package itself. Unfortunately, only the previous version’s lines match up with what is actually available in PHP 5.5 under El Capitan. These lines replace the corresponding lines from the previous version of Server:Įxtension=/Applications/Server.app/Contents/ServerRoot/usr/lib/php/extensions/no-debug-non-zts-20121212/pdo_pgsql.soĮxtension=/Applications/Server.app/Contents/ServerRoot/usr/lib/php/extensions/no-debug-non-zts-20121212/pgsql.so
On El Capitan, the problem arises because of these two updated lines in the php.ini file that lives in /Library/Server/Web/Config/php:Įxtension=/Applications/Server.app/Contents/ServerRoot/usr/lib/php/extensions/no-debug-non-zts-20131226/pdo_pgsql.soĮxtension=/Applications/Server.app/Contents/ServerRoot/usr/lib/php/extensions/no-debug-non-zts-20131226/pgsql.so
The catch is that 5.2 wants newer PostgreSQL components than El Capitan’s PHP 5.5 supports - specifically, the pdo_pgsql.so and pgsql.so modules - while on Sierra an apparent oversight on Apple’s part means that macOS Server-specific configuration details for PHP don’t get loaded at all.
If you really have to run 5.2 on Sierra, here’s a hacky fix.Īlthough in theory macOS Server 5.x is OS-independent, in practice the 5.2 update runs into problems regardless of whether it’s running on El Capitan or Sierra. On El Capitan, macOS Server 5.2 wants a mismatching PHP component, and on Sierra, 5.2’s PHP configuration is ignored by the operating system.