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 = 1551 Agreed 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 to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us .
Associated Messages, from the most recent to the oldest:
1551 Agreed 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 to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug 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:
Languages (1997)
WebCat2b12 CGI Mac - [shownext] problem (1997)
PCS Frames (1997)
Ken's Data Manager (was dbQuickView 2.0) (2005)
Finding max value for a field (1997)
5.0 Pricing (2003)
[WebDNA] Happy St. Patricks Day WEBDNA (2018)
[WebDNA] [createdate] displays today's date on Ubuntu 14.04 / WebDNA Server 8.? (2014)
Blowback and budgets. (2000)
Problems with cybercash (2000)
Newbie problem blah blah blah (1997)
ShowNext Command (1997)
Extended [ConvertChars] (1997)
WebMerchant Error (1998)
New public beta available (1997)
Text data with spaces in them... (1997)
[WebDNA] OT survey .... (2012)
pop up menu's (1998)
[WebDNA] php -> WebDNA: Can I do this with [tcpconnect]? (2013)
Search results templates (1996)