> Thanks but, this is my friend's server and I just talked to him on the
> phone. He said that he didn't want to give me total access (to Apache)
> because he didn't want me to break his server. I respect that and,
> will have to wait a couple of day to have all my domains and client's
> domains get transferred to my new box. In the meantime, he says the
> box IS configured for PHP correctly but, that I need to "hack" on it
> to get Cake to work properly.

He is incorrect. Correctly configured PHP will never (and I mean
never) offer up source code for a .php file. The problem most likely
lies in Apache, which is not putting the file through PHP, but it
falls under PHP configuration to make sure it's functioning through
the server environment.

And as has been said before, there is no real "installing" for
CakePHP. It's PHP so by nature is dynamically loaded on requests. You
just drop in the files and load the page. At most you have to set a
few paths. This method has some pros and cons, but it definitely makes
deployment easy. You'll find that out soon enough though, as soon as
PHP works for you it should be easy to get CakePHP rolling.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to