I've had a development web server running for years on Lion but recently upgraded to Sierra. Seemed to go smoothly at the time but just recently it has gone haywire (I expect as a result of macOS 10.12.2 Update).
The issue seems to be the location of Apache2. Previously it was in:
/private/etc/
But recent macOS Server versions have used:
/Library/Server/Web/Config/
Unfortunately with this new update macOS Server seems to be confused about it's location. Much of the GUI affects files in /Library/Server/Web/Config/apache2 but the version that seems to run at startup is in /private/etc/apache2 so changes have no eefect on the running version.
Is this a known issue? Is a fix in the works?
What I really need to know is where is the configuration that tells Apache to launch on startup? It doesn't appear to be a .plist in the LaunchDaemons folder. i need everything to be /Library/Server/Web/Config/apache2 so my GUI is functional and I can get back to development.
Any help would be appreciated.
The issue seems to be the location of Apache2. Previously it was in:
/private/etc/
But recent macOS Server versions have used:
/Library/Server/Web/Config/
Unfortunately with this new update macOS Server seems to be confused about it's location. Much of the GUI affects files in /Library/Server/Web/Config/apache2 but the version that seems to run at startup is in /private/etc/apache2 so changes have no eefect on the running version.
Is this a known issue? Is a fix in the works?
What I really need to know is where is the configuration that tells Apache to launch on startup? It doesn't appear to be a .plist in the LaunchDaemons folder. i need everything to be /Library/Server/Web/Config/apache2 so my GUI is functional and I can get back to development.
Any help would be appreciated.