On =Sep 23, 2016, at 10:35 AM, Kenneth Grome <ken@webdnasolutions.com> wrote:I personally don=E2=80=99t= see ANY reason why WebDNA FastCGI can=E2=80=99t 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 <talk@webdna.us>.
To =unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
|
On =Sep 23, 2016, at 10:35 AM, Kenneth Grome <ken@webdnasolutions.com> wrote:I personally don=E2=80=99t= see ANY reason why WebDNA FastCGI can=E2=80=99t 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 <talk@webdna.us>.
To =unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
DOWNLOAD WEBDNA NOW!
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...