That only works if all are upgrade and deployed with the very same cake core version. But if thats the case, you can use a single app
For smaller websites using the same core I always just had a single instance of it (without any symlinking or other setup) - zero configuration needed: ROOT/app1 ROOT/app2 ROOT/app... (to unfinitiy) ROOT/lib/Cake ROOT/plugins ROOT/vendors On the other side, a cake core (without tests and other baggage) is only 2MB. Wouldn't be that big of an overhead if you got the deployment scripts for automation. Am Freitag, 27. September 2013 23:03:15 UTC+2 schrieb WebA: > > Hello, > > We have a shared hosting server that hosts many domains (we will assume > that the amount will be scalable). We develop a Cake application and each > domain has a copy of the application's files. Each copy of the application > connects to each domain's database. > > Deploying updates to each domain is an incredibly tiresome and tedious > process. We want to consider alternative setups that will make this > process easier. > > We have thought of one alternative, but are unsure of the scalability of > them: > > - Place one copy of the Cake application on the server and create sym > links for the shared files. Domain specific files will of course be > unique > for each domain > > Has anyone had a similar issue or experience? > If anyone has any suggestions or previous experience with a similar issue, > please share! > -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups "CakePHP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/cake-php. For more options, visit https://groups.google.com/groups/opt_out.
