Command line support (request/response/routing)

[mailing_lists@…]

This is my stab at implementing a console request/routing/response. With routing, the command gets called like this:

cli.php <command> -param1 paramvalue1 -param2 -param3 paramvalue3

Without routing, the call is like this:

cli.php <module.action> -param1 paramvalue1 -param2 -param3 paramvalue3

All arguments that start with a dash(-) or double dash (--) will be regarded as paramname and the following argument as param value if it does not start with a dash or double dash. Parameters that have no following argument will be set to "true" to indicate that they have been passed.

[mailing_lists@…]

a patch to enable console apps

[mailing_lists@…]

forgot to mention: the patch introduces a new execution type, executeConsole() which falls back to execute() if not declared in the action.

[mailing_lists@…]

You must add this to the factories.xml to make the console env work

	<configuration context="console">
		<request class="AgaviConsoleRequest" />
		<routing class="AgaviConsoleRouting" />
		<response class="AgaviConsoleResponse" />
	</configuration>

[ross]

I've adding a new patch - Console.patch.txt. (You might want to split it up into parts before applying to your code base) If needs be I can add the files separately - just ask!

OK - the console files live in app/lib/console and have to be added to autoload.xml There are some changes and by default it calls the console method - I have extended the ProjectBaseAction? to have a handler for executeConsole - so you override that an your away.

The factories.xml has a bit more information in it, like turning off sessions, other than that its much the same as the original - just some extra methods in the core Console classes that were missing.

I've also added an example route in routes.xml which is called from the commandline like so:

   /pub/cli.php /cron/tag_cloud/

[ross]

Updated Console patch

[ross]

Ok adding all the files separately!

[ross]

app/config/autoload.xml

[ross]

app/config/factories.xml

[ross]

app/lib/console/ConsoleRequest.class.php

[ross]

app/lib/console/ConsoleResponse.class.php

[ross]

app/lib/action/ProjectBaseAction.class.php

[ross]

pub/cli.php

[ross]

Updated ConsoleRouting? so can generate web routes - I needed to generate links in emails sent via a cron job.

Its very basic - but can easily be extended - use AgaviWebRouting? as an example.

I also added a console.xml file to store the basic path information i.e.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<configurations>
  <configuration>
    <path>http://www.agavi.org/</path>
   </configuration>
</configurations>

Again this can easily be extended!

[jake]

I am using this configuration successfully with a few slight modifications. I had to update the config_handlers.xml as follows:

<?xml version="1.0" encoding="UTF-8"?>
<configurations xmlns="http://agavi.org/agavi/1.0/config" parent="%core.system_config_dir%/config_handlers.xml">
        <configuration>
                <handlers>
                        <handler pattern="console.xml" class="AgaviReturnArrayConfigHandler" />
                </handlers>
        </configuration>
</configurations>

I also updated the ConsoleRouting? class to fix some broken usages of the AgaviWebRouting? class that my models were making.

This works great for allowing unit tests to successfully run.

[david]

not strictly necessary for 1.0

[david]

(In [3584]) Command line support (request/response/routing), closes #480

[david]

(In [3608]) shell exit code support for command line response, refs #480