4 ms·

What kind of actions? Response handlers (edit: should have said request handlers)?

• dllthomas 11y ago
  "Actions" in a domain-relevant sense, not so much a technical one. I want the framework to help me assure that anything users can do from within the web app they can also do from a CLI client (possibly decomposed differently). My biggest objection to web apps is an extension of my objection to applications in general: because the individual steps of my workflow aren't exposed to the shell, I can't manipulate, script, and compose them as I do other sorts of actions.
  • codegeek 11y ago
    Laravel (PHP) does this well with their lovely "artisan" tool. You can pretty much call any action through "php artisan ..." including an actual CLI called tinker.
    • dllthomas 11y ago
      From what I've read, it seems targeted at site administrators and would not really be appropriate for end users (exposes the DB, &c). Is that correct? I'm thinking more something like Phabricator's arcanist (but more complete).
  • ralmidani 11y ago
    Wow. Interesting idea. I suspect it's not currently supported because web app developers are not expected to work at such a low level. The closest thing I can think of is if your back-end is simply a JSON API, you can use a tool such as cURL or httpie to make requests from the command line.
    • dllthomas 11y ago
      The shell doesn't have to be low-level. Curling the end-points directly probably would be. A client utility could wrap up higher level actions (which may involve hitting several end-points) with with a clean UI.