You should treat the two as separate apps and either try to create a data bridge between the two (with CakePHP reading from userCake), or transfer all your users from userCake to CakePHP and have a single app.
-- It also depends on your app's goals. CakePHP has an easily extendable Users plugin you could start off with. But don't mix the two if you don't really know what you are doing.
On the plus side, you could easily replicate the userCake SQL schema and data in CakePHP by connecting Cake to the database and using command line $ cake bake to replicate the data structure, since userCake uses table and field naming conventions also present in Cake.
CakePHP is also much much stronger on the security side of things.
If you really wish to use both, you should put the userCake folder inside the app/webroot folder and access it from myapp.url/userCake/ . Just make sure you use different table prefixes to avoid them from clashing.
CakePHP is also much much stronger on the security side of things.
If you really wish to use both, you should put the userCake folder inside the app/webroot folder and access it from myapp.url/userCake/ . Just make sure you use different table prefixes to avoid them from clashing.
Happy coding!
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 cake-php+unsubscribe@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment