Re: re-skinned or plugin version or my site.. like an API but templated
Thanks, I think it might need to be via an API seeing it needs to be apart of their actual website. Does anyone know of any tutorials online covering creating an API with cakephp so I can look into this further? It's all very new to me, I have used API's but never created one with or without cake. On Tuesday, 3 July 2012 14:07:37 UTC+10, Greg wrote: So you want to have essentially 1 instance of your application running (the model, and controllers), but different views (or perhaps, just a different template) at the other end? There are many ways to do this i suppose. If you host everything yourself you can probably use App::build to point at a central/reusable set of models/controllers etc for a given domain. Or you could go the other way, and change the template view path based on the request.. if you want them to physically host the front end, then you probably need to use an actual API - expose your backend as a restful api (which is a snap in cake to do), and write a front end app which consumes that API - customise the front end app with various styles etc. They can then install your front end application on their servers and get at it from something like http://clienturl/yourapplication Hi All, I am about to being a projest with cakePHP as the framework, my client has now asked me how we can go about setting up the site so other firms in the same industry could somehow use the same system (running on our database) from a front end point of view on their website as an addon product. So basically the front end of the site will be designed for us and then again for each of the other firms but the functionality and admin remain the same which they plugin to their site (nearly like using old school iframes). Any ideas on how this could best work and be setup initially? Almost like an API but the whole front end needs to be templated with their corporate colours and logo (I'm thinking custom header and footer then the content area remains quite neutral) Any tips or threads, posts etc online would be great. Thanks -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. 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 -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. 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
Re: re-skinned or plugin version or my site.. like an API but templated
cake pretty much provides an api out of the box for each of your controllers. Look at the relevant chapters on REST in the book. Essentially you configure the request handler and turn on parse extensions and do some minor tweaking in the controller logic.. so if someone hits http://yourwebsite.com/posts/ in a browser they get the rendered html if they hit http://yourwebsite.com/posts.json they get a json object posts.xml they get an xml object etc etc. writing a front end at the other side to deal with it would require either some form of REST datasource to rehydrate the json as data inside models for you to use, or some other solution to consume the services. On Wed, Jul 4, 2012 at 7:23 AM, elogic asymo...@elogicmedia.com.au wrote: Thanks, I think it might need to be via an API seeing it needs to be apart of their actual website. Does anyone know of any tutorials online covering creating an API with cakephp so I can look into this further? It's all very new to me, I have used API's but never created one with or without cake. On Tuesday, 3 July 2012 14:07:37 UTC+10, Greg wrote: So you want to have essentially 1 instance of your application running (the model, and controllers), but different views (or perhaps, just a different template) at the other end? There are many ways to do this i suppose. If you host everything yourself you can probably use App::build to point at a central/reusable set of models/controllers etc for a given domain. Or you could go the other way, and change the template view path based on the request.. if you want them to physically host the front end, then you probably need to use an actual API - expose your backend as a restful api (which is a snap in cake to do), and write a front end app which consumes that API - customise the front end app with various styles etc. They can then install your front end application on their servers and get at it from something like http://clienturl/**yourapplication Hi All, I am about to being a projest with cakePHP as the framework, my client has now asked me how we can go about setting up the site so other firms in the same industry could somehow use the same system (running on our database) from a front end point of view on their website as an addon product. So basically the front end of the site will be designed for us and then again for each of the other firms but the functionality and admin remain the same which they plugin to their site (nearly like using old school iframes). Any ideas on how this could best work and be setup initially? Almost like an API but the whole front end needs to be templated with their corporate colours and logo (I'm thinking custom header and footer then the content area remains quite neutral) Any tips or threads, posts etc online would be great. Thanks -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscribe@**googlegroups.comcake-php%2bunsubscr...@googlegroups.comFor more options, visit this group at http://groups.google.com/**group/cake-phphttp://groups.google.com/group/cake-php -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. 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 -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. 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
re-skinned or plugin version or my site.. like an API but templated
Hi All, I am about to being a projest with cakePHP as the framework, my client has now asked me how we can go about setting up the site so other firms in the same industry could somehow use the same system (running on our database) from a front end point of view on their website as an addon product. So basically the front end of the site will be designed for us and then again for each of the other firms but the functionality and admin remain the same which they plugin to their site (nearly like using old school iframes). Any ideas on how this could best work and be setup initially? Almost like an API but the whole front end needs to be templated with their corporate colours and logo (I'm thinking custom header and footer then the content area remains quite neutral) Any tips or threads, posts etc online would be great. Thanks -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. 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
