Re: [WebDNA] Apple nixes Mac OS Server ("websites") and other
This WebDNA talk-list message is from 2018
It keeps the original formatting.
numero = 113951
interpreted = N
texte = 1551Agreed with Michael: the WebServer from Apple is a very personalized =version of a "normal" webserver (linux) and the documentation is very =weak. For instance, the last High Sierra version uses an almost =undocumented local proxy that does not return all the information WebDNA =is expecting from apache.We will design a new installer for the next version, but more than ever =it will run on a clean OSX server installation. It will be too =complicated to take a specific customization into account.I strongly suggest linux, it is safe, cheaper, faster and not more =difficult to manage.- chris> On Jan 29, 2018, at 23:35, Michael Davis
wrote:>=20> Palle,>=20> Personally, I will be glad to have Apple keep their hands off of =Apache. The Server.app has always been geared toward internal LAN =services rather than as a "control panel" that might help those of us =that serve web sites publicly. Their squid cache setup has just =convoluted the 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. Can't do it). 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 or whether there will still be custom conf =directories that tie http services to some other service.>=20> 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 =Apple gets out of the way in the Apache conf directory.>=20> Like I said, I'm glad to see them step away from the web services, as =the Server.app has slowly become more crippled over the years, with each =update removing functionality, rather than adding it. Just try =monitoring your smtp queue in Server.app 5 for instance. It's no longer =there. So I welcome Apple staying away from Apache and allowing me to =configure it without worrying about whether the conf files are going to =be overwritten by the Server.app.>=20>=20> Mike---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leave@webdna.usarchives: http://www.webdna.us/page.dna?numero=3D55Bug Reporting: support@webdna.us.
Associated Messages, from the most recent to the oldest:
1551Agreed with Michael: the WebServer from Apple is a very personalized =version of a "normal" webserver (linux) and the documentation is very =weak. For instance, the last High Sierra version uses an almost =undocumented local proxy that does not return all the information WebDNA =is expecting from apache.We will design a new installer for the next version, but more than ever =it will run on a clean OSX server installation. It will be too =complicated to take a specific customization into account.I strongly suggest linux, it is safe, cheaper, faster and not more =difficult to manage.- chris> On Jan 29, 2018, at 23:35, Michael Davis wrote:>=20> Palle,>=20> Personally, I will be glad to have Apple keep their hands off of =Apache. The Server.app has always been geared toward internal LAN =services rather than as a "control panel" that might help those of us =that serve web sites publicly. Their squid cache setup has just =convoluted the 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. Can't do it). 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 or whether there will still be custom conf =directories that tie http services to some other service.>=20> 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 =Apple gets out of the way in the Apache conf directory.>=20> Like I said, I'm glad to see them step away from the web services, as =the Server.app has slowly become more crippled over the years, with each =update removing functionality, rather than adding it. Just try =monitoring your smtp queue in Server.app 5 for instance. It's no longer =there. So I welcome Apple staying away from Apache and allowing me to =configure it without worrying about whether the conf files are going to =be overwritten by the Server.app.>=20>=20> Mike---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leave@webdna.usarchives: http://www.webdna.us/page.dna?numero=3D55Bug Reporting: support@webdna.us.
christophe.billiottet@webdna.us
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
writing db to disk (1997)
WebDelivery downloads alias, not original ? (1997)
More NT encyption!! (1999)
Install Webcatalog under NT4.0 and Microsoft IIS 2.0 (1997)
CC Payment Processors (2007)
Stumpted Again (1997)
Gremlins, huh? (2000)
RE: speed of TCPConnect? (1998)
View order not right (1997)
Encryption Question (2006)
I'm new be kind (1997)
Search for 20 finds ... Eureka! (1997)
Expert tech support -- a fast and simple solution (long) ... (2000)
Listserver problem (1997)
Cart ID Duplication (2001)
cart converting to scientific notation format (2001)
WebCat2b13MacPlugIn - [include] (1997)
[WebDNA] Math variable name length limitations ... (2012)
Robert Minor duplicate mail (1997)
[WebDNA] Putting '&search' into URL killing all search contexts (2010)