[WebDNA] My failed cPanel and WebDNA experience ...
This WebDNA talk-list message is from 2016
It keeps the original formatting.
numero = 113003
interpreted = N
texte = 591 > I personally don=E2=80=99t see ANY reason why WebDNA FastCGI can=E2=80=99= t be > installed on a CPANEL Account. Years ago when I tried to get WebDNA running on a cPanel server I learned that: 1- cPanel has its own internally hard-coded versions of some of apache's config files. 2- cPanel systematically overwrites these apache config files with its internally hard-coded versions, presumably to insure that no one can manually edit and possibly "screw up" these apache config files and inadvertently break cPanel. 3- When cPanel overwrites apache's config files, the required WebDNA directives in those files are deleted. This immediately breaks WebDNA while insuring that cPanel keeps working properly. So ... If you can gain access to cPanel's internally hard-coded apache config templates, and modify them by adding the directives required by WebDNA, then each time cPanel overwrites apache's config files it will preserve (rather than delete) the required WebDNA directives -- and finally you'll have a server that runs both cPanel and WebDNA together in a compatible manner. I certainly wish you the best of luck in your efforts to accomplish this task, assuming you try it some day. Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Administration --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us .
Associated Messages, from the most recent to the oldest:
591 > I personally don=E2=80=99t see ANY reason why WebDNA FastCGI can=E2=80=99= t be > installed on a CPANEL Account. Years ago when I tried to get WebDNA running on a cPanel server I learned that: 1- cPanel has its own internally hard-coded versions of some of apache's config files. 2- cPanel systematically overwrites these apache config files with its internally hard-coded versions, presumably to insure that no one can manually edit and possibly "screw up" these apache config files and inadvertently break cPanel. 3- When cPanel overwrites apache's config files, the required WebDNA directives in those files are deleted. This immediately breaks WebDNA while insuring that cPanel keeps working properly. So ... If you can gain access to cPanel's internally hard-coded apache config templates, and modify them by adding the directives required by WebDNA, then each time cPanel overwrites apache's config files it will preserve (rather than delete) the required WebDNA directives -- and finally you'll have a server that runs both cPanel and WebDNA together in a compatible manner. I certainly wish you the best of luck in your efforts to accomplish this task, assuming you try it some day. Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Administration --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us .
Kenneth Grome
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:
Just Testing (1997)
Extra carriage returns (1999)
Include remote? (1998)
Weird happenings when viewing in IE 3.02 (1998)
WebCat.acgi from /cgi-bin/? (1997)
WebCat2: multiple currency support (1997)
Trigger Problems (2000)
Webcat no longer supported? (2006)
CMSBuilder (2004)
Follow-Up to: Removing [showif] makes a big difference in speed (1997)
Temp DB (Was freeze) (2003)
Shipping.db (1998)
syntax question, not in online refernce (1997)
date pref (1999)
Fun with dates (1997)
Stopping bad HTML propagation ? (1997)
WebCat2b12 - New features for 1.6 users ... (1997)
WebCat2 beta FTP site (1997)
Archives... (1997)
WC2.0 Memory Requirements (1997)