Hi beneroth, On Tue, Sep 03, 2019 at 05:35:02PM +0200, [email protected] wrote: > psh (located in the bin/ dir within picolisp/ > dir) is "picolisp shell" (or process shell?), > is a tool to get a REPL to a running picolisp > app process. > The implementation is a bit tricky, basically > it does a HTTP request to the running app > server (to initiate a session process), > and then that process gets told to bind to a > tty, so you get a REPL to the running > application - a child process, same as normal > application user sessions, not the master > process. > > So with psh you can work on the live application, like just another user.
Correct. Let me note that in addition to what you described, i.e. starting a *new* session in a running server with $ bin/psh 8080 or $ bin/psh <httpGateName> you can now also connect directly to an already *running* GUI session with $ bin/psh 52545 12899978148913174~ where "52545" is the port and "12899978148913174~" the session ID of that process. They are known because the (app) function prints them to stderr (to terminal during development and log file in production) in the form 19505 = 52545 12899978148913174~ where "19505" is the PID. ☺/ A!ex -- UNSUBSCRIBE: mailto:[email protected]?subject=Unsubscribe
