You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Scheduled Shutdown Should Not Shutdown If There Are Active SSH Connections #3191
I was working on my Coder workspace instance which is scheduled to shut down at 5:00 PM. Right as 5:00 PM came by my editor froze up and my SSH terminal closed its connection.
In the future I will give myself an extra hour in the schedule to prevent this. But I feel like if I have established an SSH connection via the Coder CLI and it is still open the instance should not shut down.
We're considering a different model for autostop which stops the workspace after n hours of inactivity, or keeps a workspace alive, despite a schedule being present: #2995. What do you think of this?
That could be good. I do like the schedule so that my workspace doesn't shut down during lunch or during a meeting heavy day. Mainly because there are some development tasks (👀 webpack) that take a few minutes to start up with a big app. So having the workspace up and the tasks already running saves time. Additionally having the scheduled start at 9:00 AM is nice because I know that by the time I start dev work after standup all those tasks will be running and good to go.
For my particular use case I think being able to configure only having keep alive functionality and not inacitvity shutdown would be nice.
Activity
Mainstay-Noah-Huppert commentedon Jul 25, 2022
Coder server v0.7.12
Mainstay-Noah-Huppert commentedon Jul 25, 2022
bpmct commentedon Jul 25, 2022
We're considering a different model for
autostopwhich stops the workspace after n hours of inactivity, or keeps a workspace alive, despite a schedule being present: #2995. What do you think of this?Mainstay-Noah-Huppert commentedon Jul 25, 2022
That could be good. I do like the schedule so that my workspace doesn't shut down during lunch or during a meeting heavy day. Mainly because there are some development tasks (👀 webpack) that take a few minutes to start up with a big app. So having the workspace up and the tasks already running saves time. Additionally having the scheduled start at 9:00 AM is nice because I know that by the time I start dev work after standup all those tasks will be running and good to go.
For my particular use case I think being able to configure only having keep alive functionality and not inacitvity shutdown would be nice.
ammario commentedon Jul 26, 2022
@Mainstay-Noah-Huppert thank you for the feedback. Let's move the discussion here.