what kind of deployment problems are you talking about?  as for right
now, i am hosting everything myself.. so i really do need to have
separate discrete apps on one server.  at any rate, i ended up using
something like a combination between production and development setup
using symbolic links from each app to the cake main directory outside
the document root.. so i have something like:

/var/www
     + public_html
          + app1
               + app
               + cake -> /var/www/cake_1.2.1.8004/cake/
               - index.php
               + vendors -> /var/www/cake_1.2.1.8004/vendors/
          + app2
          + non-cake app
          (etc)
     + cake_1.2.1.8004

i'm not sure if this is the best way to do it or not, but it seems to
work fairly well so far.

On Mar 23, 10:05 pm, brian <bally.z...@gmail.com> wrote:
> I'm sure this can be done but I have to wonder if it's a good idea.
> Making a single core library is one thing, but what you're describing
> seems like a recipe for deployment problems down the road.
>
> When I first started fiddling with Cake, my first inclination was to
> centralise the core libs. However, I came to realise that it's a whole
> lot easier to include the libs separately for each project because I
> won't be hosting them all myself, so I've changed everything to do
> that. Although there's a bunch of duplicated files on my server, each
> site is that much easier to move around.
>
> On Mon, Mar 23, 2009 at 6:51 PM, matt <gonnawaitit...@gmail.com> wrote:
>
> > hi all, i'm pretty new to cakephp and i'm having a difficult time
> > getting it setup the way i want.
>
> > just to test, i originally set it up using the "production" method,
> > went through the blog tutorial, and everything was working fine.
>
> > now i need to reorganize things so that:
>
> > - i can create separate discrete cake applications on my server.  they
> > will have URLs like mydomain.com/app1, mydomain.com/app2, etc
> > - all applications share the same cake core files
> > - the document root is at the same level as the cake directory
>
> > the structure i want would look something like this:
>
> > /var/www
> >     + public_html (contains all publicly accessible files)
> >          + app1
> >               - index.php
> >               + css
> >               + img
> >               (etc)
> >          + app2
> >     + cake (contains cake core and app files)
> >          + cake
> >          + apps
> >               + app1
> >                    + config
> >                    + controls
> >                    (etc)
> >               + app2
>
> > (i hope that formats correctly, there doesn't appear to be a preview
> > option)
>
> > i changed the options in public_html/app1/index.php to point to the
> > cake core and my app directory, and the index (at mydomain.com/app1)
> > file loads just fine with the database message, etc.  but when i go to
> > mydomain.com/app1/posts to view the data from the blog tutorial i get
> > a file not found error.
>
> > i hope i'm missing one small step.. any ideas?

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to 
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to