I basically want to share the app and cake folder of an application,
so that the only thing that needs to be uploaded for a new instance of
the app is the webroot folder. To complicate matters slightly caching
is utilised, so the tmp folder needs to be moved to the webroot (as
well as the config f
On Sat, Sep 26, 2009 at 11:18 AM, number9 wrote:
>
> I basically want to share the app and cake folder of an application,
> so that the only thing that needs to be uploaded for a new instance of
> the app is the webroot folder. To complicate matters slightly caching
> is utilised, so the tmp fold
Cool - got it working (at least locally). here's my setup:
AppServ\www\cake\
AppServ\www\cake\cake\
AppServ\www\cake\docs\
AppServ\www\cake\vendors\
AppServ\www\cake\index.php
AppServ\www\acakesite\app\config\
AppServ\www\acakesite\app\controllers\
AppServ\www\acakesite\app\models\
AppServ\www\
> Once the local testing is done, how would the actual production site
> be configured?
> can the cakephp libs/core be hidden one directory above the www on the
> production servers?
yes, this I think would be considered best practice. Just move the
cakephp dir to the same level as www (not insid
Once the local testing is done, how would the actual production site
be configured?
can the cakephp libs/core be hidden one directory above the www on the
production servers?
on a related note, are there any disadvantages of the cakephp libs/
core being placed one directory above the public_html
> D:\AppServ\www <-- http docs root (localhost)
> D:\AppServ\www\onesiteroot <-- one web project
> D:\AppServ\www\anothersiteroot <-- another web project
> D:\AppServ\www\heresanothersite <-- yet another web project
this is very easy, place cakephp dir (inc app, webroot etc) in the
root of yo
Thanks for the reply, guys...
Well, I use AppServ at home (much smaller and 'simpler' than Xampp...
www.appservnetwork.com ).
Been using that for the past 4 years (all PHP stuff)...
Since a lot of my projects are becoming quite large and complicated,
instead of myself building my own framework, I
I'm with kabturek on this one. I'd stick with the initial download
setup until you learn the ins and outs of cake and its structure. It's
simple, just drop the whole download into a folder accessible by your
browser, make sure mod_rewrite is on, set up your database.php file
in /app/config/ and yo
>From what you've written you seem to want to develop an app - woudn't
it be wiser to use the *developement* setup ? ;) probably on your home
machine ? You want a production setup for dev ... imo you should
stick with the basic setup for now - and when you actually learn cake
- there is no proble
What if I did NOT want the webroot files to be at the actual webroot
(at least during develpment/testing, where there are multiple websites
on a shared server?)
i.e. How can I move the /cake_install/app/webroot files into /
public_html/app/webroot WITHOUT having to set the actual www webroot
to b
This is the structure that I was thinking of...
/cake/cake/
/cake/cake/config/
/cake/cake/docs/
/cake/cake/libs/
/cake/cake/scripts/
/cake/cake/app_controller.php
/cake/cake/app_model.php
/cake/cake/basics.php
/cake/cake/bootstrap.php
/cake/cake/dispatcher.php
/cake/vendors/
/public_html/app/ <-
I'm new to CakePHP - ready to learn it - so I'm trying to set it up on
a shared hosting account.
currently, when I log into my account via FTP, i get into one level
above the public_html (webroot).
I'd like to put the CakePHP libraries/framework there... and all of
the site's stuff (i.e. "apps/v
12 matches
Mail list logo
