Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Decouple terminal sessions from connections #68
There are several possible issues that can result in the ssh session dying after 1 a minute or two disconnected from the network.
The problem with the app as it is written is that the ssh session
Instead, terminal sessions should be stored in a hash like object with a key being a unique identifier that is shared with the client so that the client can use that identifier when it tries to initiate a new ws connection. Then the new ws connection would have three possiblities:
With this work we still have the problem of the web server itself being killed by Passenger after the
In the PUN configs, it seems that we are using default values for these:
And for the shell app only we could consider setting passenger_min_instances to 1:
Would this ensure that the for any user running a shell app that PUNs and the shell app stick around, even after users go away from the app? Forever?
We might want to consider when we would want to ensure shell apps actually get shut down.