To update the PHP used by the Server.app:ġ. Browse to your_server_url/info.php and view the phpinfo() for your server. The general advice is not to modify files in this directory, however to view the php configuration, you can safely edit the 'info.php' file (sudo required) and uncomment the 'phpinfo() ' line. This configures two default Server 'Websites:' by default here: /Library/Server/Web/Data/Sites/Default. Add your domain and allow the service to configuration DNS. The Liip PHP patch does not modify the Server.app PHP references so additional actions are required to make it work. I was able to make a solution that works an I understand. Solution chosen: LiiP because they provide a single line installer and the help I found more understandable than the MacPorts and Homebrew streams. I didn't want another layer of complexity (as I saw it). Why use MacOS Server rather than a MAMP or similar install? For me I was using Server and it was the relative ease of Server control and configuration of Mac Airport router which can be managed from within the Server console (no more rebooting of the router when changes are made). This introduces a few additional steps to get it working with the desired version of PHP. The MacOS Server is a standalone application that runs its own Apache server configuration independently from the underlying MacOS Sierra (10.12) Apache configuration. Problem: The basic Server.app configuration lacks support for PHP Intl and I could find no way (within my capability) of compiling and linking intl.so. Hardware: Mac Mini (late 2012), 2.6GHz Core i7, 16GB Ram, running MacOS Sierra Server 5.3.1 The web site needs to be accessible eternally (not just through localhost). Motivation: I wanted to run a PHP web app that requires the php intl extension. Here is how I solved the problem of PHP limits in the vanilla Server.app. Is the only viable solution to ignore the server app and install a MAMP server? Please accept my apologies if that is a dumb conclusion - I'm still climbing the learning slope. Is that possible? Are there likely to be unintended but foreseeable consequences? Presumably a system update might result in the apache nf file being overwritten but that would, I assume, not be a significant issue providing I restored the settings following an upgrade.Īs an aside, presumably there are many international users of the Server app and yet there is no inbuilt support (I can discover) for the PHP-Intl extension. Presumably that'll involve editing the apache nf file but this is where my lack of knowledge lets me down. I am wondering whether a practical solution would be to have the Server Apache use a custom PHP version (Macports/Homebrew/Fink etc). Since I want to make use of the native server apps and a web-app that requires php-intl, I don't want to replace the server app with a MAMP installation. I also hear load and clear that it is best not to mess with the inbuilt files for many reasons, not least being the fact that come the next update any changes are likely to be overwritten. I can see there are two php instances, one associated with the Server app and the other with the underlying OS. Thanks John and scott_mdm for you responses,
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |