On Mon, Jan 29, 2018 a=t 8:35 PM, Michael Davis
<admin@network13.net> wrote:
<=blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">Palle,
Personally, I will be glad to have Apple keep their hands off of Apache.=C2==A0 The Server.app has always been geared toward internal LAN services rath=er than as a "control panel" that might help those of us that ser=ve web sites publicly.=C2=A0 Their squid cache setup has just convoluted th=e conf files and made it harder to run a professional level web host (just =try changing ports on these services, for instance because you want to run =your own accelerator cache like Varnish on port 80.=C2=A0 Can't do it).==C2=A0 What remains to be seen is whether discontinuing the websites in the= Server.app will actually free up Apache from the mungling hands of Apple o=r whether there will still be custom conf directories that tie http service=s to some other service.
If you like using the Apple GUI to manage web sites, you'll probably be= even happier with the WebMin GUI, which you would be free to use once Appl=e gets out of the way in the Apache conf directory.
Like I said, I'm glad to see them step away from the web services, as t=he Server.app has slowly become more crippled over the years, with each upd=ate removing functionality, rather than adding it.=C2=A0 Just try monitorin=g your smtp queue in Server.app 5 for instance.=C2=A0 It's no longer th=ere.=C2=A0 So I welcome Apple staying away from Apache and allowing me to c=onfigure it without worrying about whether the conf files are going to be o=verwritten by the Server.app.
Mike