Keeping a site going through the Node.js update

[NoUserName]

Does

• After you’ve updated a deprecated Node version, the project container will need to go to sleep for the actual update to take place. This can take up to 12 hours, especially if it’s a boosted project. https://help.glitch.com/hc/en-us/articles/16287495688845-What-version-of-Node-can-I-use-and-how-do-I-change-update-upgrade-it

mean that there’s no way to keep my site running through this upgrade? I.e. it has to come down for up to 12 hours?

[jenn]

Hi there - yes, unfortunately the project would need to be restarted for the change to take place and the restart may take up to 12 hours to happen - it wouldn’t take down the site for an additional 12 hours. If you let me know the name of your project I can do it manually for you right now.

[NoUserName]

the restart may take up to 12 hours to happen - it wouldn’t take down the site for an additional 12 hours

Sorry, I don’t understand. What’s the max period the site would be down for?

[jenn]

When you update the version of Node, it doesn’t register until the container restarts or falls asleep. Most projects fall asleep after several minutes of inactivity - once they wake up they will have registered the new version of Node you chose. But boosted projects do not fall asleep with inactivity - they do restart around every 12 hours, which is where that maximum came from.

[NoUserName]

I see. Thanks.