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:
RE: Writefile outside WebSTAR hierarchy? (1997)
Not really WebCat (1997)
update on wn searching (1997)
Free WebDNA snippets (Extending WebCatalog) (1997)
RAM variables (1997)
Location of Webcat site in folder hierarchy (1997)
question: search return in order (1997)
[WebDNA] [append] does not add the newline char at the end of the new record?! (which causes subsequent [search] to fail.) (2009)
Re:Searching for ALL / empty form field (1997)
[protect] on NT? (1997)
WebCatalog for guestbook ? (1997)
Add a field to the error log? (1997)
WebMerchant 2.1.2 (1998)
Help name our technology! I found it (1997)
Checkboxes (1997)
Budget system (2003)
Snake Bites (1997)
View a Order file (1999)
Pre-flight public flag (1997)
Duplicate Cart Numbers (1999)