Re: [WebDNA] My failed cPanel and WebDNA experience ...
This WebDNA talk-list message is from 2016
It keeps the original formatting.
numero = 113006
interpreted = N
texte = 594I haven=E2=80=99t looked at the install script, but I=E2=80=99ll bet it =could be simplified.> On Sep 23, 2016, at 10:53 AM, christophe.billiottet@webdna.us wrote:>=20> apache 2.4 and recent linux do not anymore rely on what is written in =the httpd.conf : this file is now pretty much static; it includes folder =content in which each vhost config is stored, as well as extra =configuration. This is the place to store WebDNA configuration. I guess =cPanel would be less a problem now than before.>=20> - chris>=20>=20>=20>=20>> On Sep 23, 2016, at 18:35, Kenneth Grome
=wrote:>>=20>>> I personally don=E2=80=99t see ANY reason why WebDNA FastCGI can=E2=80==99t be>>> installed on a CPANEL Account.>>=20>> Years ago when I tried to get WebDNA running on a cPanel server I>> learned that:>>=20>> 1- cPanel has its own internally hard-coded versions of some of>> apache's config files.>>=20>> 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.>>=20>> 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.>>=20>> So ...>>=20>> 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.>>=20>> I certainly wish you the best of luck in your efforts to>> accomplish this task, assuming you try it some day.>>=20>> Regards,>> Kenneth Grome>> WebDNA Solutions>> http://www.webdnasolutions.com>> Web Database Systems and Linux Server Administration>=20>=20>=20>=20> ---------------------------------------------------------> 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---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us.
Associated Messages, from the most recent to the oldest:
594I haven=E2=80=99t looked at the install script, but I=E2=80=99ll bet it =could be simplified.> On Sep 23, 2016, at 10:53 AM, christophe.billiottet@webdna.us wrote:>=20> apache 2.4 and recent linux do not anymore rely on what is written in =the httpd.conf : this file is now pretty much static; it includes folder =content in which each vhost config is stored, as well as extra =configuration. This is the place to store WebDNA configuration. I guess =cPanel would be less a problem now than before.>=20> - chris>=20>=20>=20>=20>> On Sep 23, 2016, at 18:35, Kenneth Grome =wrote:>>=20>>> I personally don=E2=80=99t see ANY reason why WebDNA FastCGI can=E2=80==99t be>>> installed on a CPANEL Account.>>=20>> Years ago when I tried to get WebDNA running on a cPanel server I>> learned that:>>=20>> 1- cPanel has its own internally hard-coded versions of some of>> apache's config files.>>=20>> 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.>>=20>> 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.>>=20>> So ...>>=20>> 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.>>=20>> I certainly wish you the best of luck in your efforts to>> accomplish this task, assuming you try it some day.>>=20>> Regards,>> Kenneth Grome>> WebDNA Solutions>> http://www.webdnasolutions.com>> Web Database Systems and Linux Server Administration>=20>=20>=20>=20> ---------------------------------------------------------> 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---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us.
Patrick McCormick
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:
remotely creating and populating a stock inventory db -almost there! (1999)
RE: Upload and WebCat (1998)
Next (1997)
Bug? (1997)
warning... Banner Rotation (2000)
boldwords (2001)
Emailer & IMail List Server (1998)
[OT] ssh user@domain.com (2004)
Date search - yes or no (1997)
Surprise x and y post args (1998)
Selected Item in Pop-down (2003)
[convertChars] and in a textarea on a form (1998)
Summ=T Problem (1997)
WebDNA update from Smith Micro (2002)
Configuring E-mail (1997)
Authorize net woes (2003)
separate by mont (search) (2002)
Two stores, one server (1998)
User/pass with tcpconnect (2000)
Locking up with WebCatalog... (1997)