If done properly, they could also be made aware of other plugin servers, so in the case that the user cannot find the plugin at the original source nor at the plugin server, a different server can kick in and act as a backup if the plugin is available there. In the case that a plugin is no longer available at it’s original source, the plugin server provider would have the option of mirroring the plugin on their own server, and also replicating it across HG and SVN, or whatever other SCM they intend to implement. The server, upon aggregating the new plugin, would attempt to mirror the plugin for future reference. So something akin to Github, except explicitly for CakePHP code. Maybe even a download in zip or tar format of the plugin. Users would also be able to browse the plugin server, check out available plugins, perhaps see screenshots or readme files where appropriate, and more information about the author. A user would be able to log onto the site, register a plugin of theirs (with the appropriate links for repository browsing, branches where necessary, dependencies, etc.) and that plugin would be available immediately via a JSON api. The server would output JSON similar to the above for each record. Ideally, the plugin would be standalone, both a server and a set of shell scripts. "repository" : "git:///cakephp/trackable-behavior.git", "description" : "Who created or modified this record?" Andy Dawson of CakePHP and Lithium fame actually was working on something of an api for this. In some cases, a plugin may require another, so just another thing to keep track of. A project has a url, a main maintainer, some branches, a readme, and perhaps some links. I personally use git, so I’m going to concentrate on that, although the paradigms are almost all the same across each platform. Regardless, it would be nice to have any code that is already plugin-ready to be available to a user via git, hg, svn etc. Feel free to contribute to Bakery 2.0 and prove me wrong :) Unfortunately, the recent split of the CakePHP Core Team between CakePHP and Lithium has me doubting that such a thing would ever happen, as Gwoo, the maintainer of, went to the Lithium camp. If this were integrated with and bakery articles, then we’d have a great potential win. a file (or package of files) within the browser. Github’s gist feature would go great with this, as it provides a nice way to diff, fork, etc. There has been a lot of snippets released, and plenty of components, behaviors, helpers on the cakephp bakery, as well as on, and even on github. I suspect this is because no one cares to release their hard-worked for code, but it doesn’t matter. Unfortunately, there hasn’t been a rash of mini-application releases. So you could build parts of your applications in plugins, then just bash them together to create websites to a clients specifications with little-to-no work. that will allow one to place this reusable code where needed, but also provides “plugins” that allow users to package up related things into neat little bundles. CakePHP provides Behaviors, Components, Helpers, etc. There are hundreds of open-source CakePHP code that would be great to use in one’s own personal web applications. The idea behind a plugin server is simple. It is neat and all, and one of the first things I came across when looking at CakePHP 11 months ago. The existing sample was created by John David Anderson of. One of my current projects is a CakePHP plugin server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |