Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use cases for Respect\Cli #1

Open
alganet opened this issue Feb 14, 2012 · 2 comments
Open

Use cases for Respect\Cli #1

alganet opened this issue Feb 14, 2012 · 2 comments

Comments

@alganet
Copy link
Member

alganet commented Feb 14, 2012

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.

@alganet
Copy link
Member Author

alganet commented Feb 14, 2012

Pinging @augustohp and @henriquemoody to check out this.

@nickl-
Copy link
Member

nickl- commented Aug 29, 2012

I shireeush Ish washn't even dare. Promish!

drumk panda

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants