respect/cli

Makes your code speak CLI

cli's Issues

Use cases for Respect\Cli

Hey guys! Let's sketch up some use cases to get a better idea of what we're going to code. Yesterday I was drunk thinking of these main scenarios:

• Automation: Users of Respect components would like to automate tasks to use on cron jobs or even manually. Using the same PHP codebase and the same INI configuration files without having to code coupled Cli logic would enable them to do so effortlessly.
• Daemonization: Bitches like daemons. We could use PEAR_System_Daemon or ressurrect Respect\Daemon (resting in peace at https://github.com/alganet/Daemon_deprecated).
• Debugging: instead of spreading out var_dump()s all around the place an user could interact with the application components by starting an interactive session inside the code dependencies. Maybe we could even save/restore debug sessions freezing out components.

Also, this is a great opportunity to create an awesome tool that uses the new bundled PHP server. We could even start an interactive PHP session that ALSO serves up the application to a browser.

Please, send all your love to this issue.