Interesting questions.
The quick answer is yes, JApplicationCli is what you'd use to build
the Joomla equivalent to Drush, but I probably wouldn't design Joosh
(?) like Drush.
What we are doing at eBay, for a project, is designing a web services
platform for next-gen sites, but we have a command line interface for
that platform as well. For example, the let's say the API for getting
an article (as a json string) is:
http:://api.url/article/123
We've made it so you can invoke that from the command line as well, like this:
$ services /v1/json/article/123
Where "v1" is the API version and "json" is the return format. The
CLI is just a proxy to the same/similar route to load the same
controller that the web service would load (two birds with one stone).
That's what I'd do if I was designing a new project or thinking about
the future of Joomla as a content delivery platform. As for
retrofitting the existing CMS with a CLI goes, that would be a big
job.
Regards,
Andrew Eddie
On 1 May 2012 13:29, Pastor Dan <pastordanwal...@gmail.com> wrote:
> Drupal has a fantastic command-line interface called Drush
> (
http://drush.ws). It seems to me that a major use of JApplicationCli in
> Joomla could be to enable a similar functionality. Basically, allow
> installation, upgrades, enabling/disabling of extensions, permission changes
> and so forth on Joomla sites via the command line. This would allow a
> developer to maintain many Joomla sites with a minimum of effort. Yet, I see
> almost nothing written about this. It seems most view the platform as a
> vehicle for building apps that have nothing to do with the CMS. What is the
> potential for building Drush-like functionality with JApplicationCli? It
> would be great if someone more knowledgeable than I could build some example
> Cli apps that allow you to perform at least some of the Drush functions on
> Joomla. If I am missing some information on this, please point me in the
> right direction.
