Library/Server/Web/Config/apache2/ReadMe.txt You can read some of the rationale behind this decision in the documentation included in the installation:
With Server 5, Apple has inserted a proxy layer between websites and the outside world, with a separate dedicated Apache instance now providing a reverse proxy, ferrying communications between the outside world and the web service Apache instance.
#OS X SERVER UPGRADE UPGRADE#
It was also necessary to create a simple MySQL launcher since it lost the ability to start up automatically (“ Installing, Configuring and Performance Tweaking MySQL for OS X Server”), and including the following little gem turned out to be rather important due to problems with AllowOverride taking on its default value:īut while it turned out there were several things that wound up being important for a smooth upgrade experience and minimal downtime, it was nothing at all like Server 5.
Sure, Yosemite made it necessary to roll back the TRIM support I’d mentioned in “ Enabling OS X TRIM Support for Non-Apple SSDs”, and yes, the new PHP opcache replaced APC (“ Boost PHP Performance on OS X by Installing APC”). In my experience, it turned out to be easier than the previous upgrade. With the previous upgrade, from Mavericks and Server 3 to Yosemite and Server 4 (which updated Apache to 2.4), I didn’t even mention the experience here on the site - in part because I waited many months before taking the plunge on anything other than a test server, and in part because once I did, there wasn’t all that much to report. Here’s one approach to handling upgrades which has worked well for the last several versions, including 5.
Version 5 of the Server app for OS X has much to recommend it, but if you host websites, you’ll need to be ready with several fixes for problems both big and small.
0 kommentar(er)
