In the Self-hosting category, user stephtara reported a failed GUI update that left the site down, asking if she should use the “big scary red button” pfaffman advised waiting until morning to attempt a command-line upgrade instead. stephtara later shared a Ruby version mismatch error and asked about running a full rebuild via the command line. ToddZ confirmed that command-line rebuilds are a reliable solution for GUI failures. After successfully rebuilding the app, stephtara expressed relief. philh and pfaffman discussed the error, while Canapin noted that while GUI updates are improving, the command-line ./launcher rebuild app is a safe and effective repair method that won’t cause data loss. merefield joked about the red button being useless, and pfaffman mentioned a dashboard tool he built to simplify command-line rebuilds.
Yeah, GUI updates can occasionally fail for various reasons, and the typical next step is a command line rebuild. In my experience that’s always cleared things up.
(And the sudo on those commands assumes you’re not logged in as the root user.)
Just writing this for the visitors who will read this topic after having themselves issues with the GUI update:
True, it seems more reliable nowadays, but I had enough issues with it in the past to often prefer using the command-line instead, even if it’s less straightforward.
If your update from the interface didn’t work, ./launcher rebuild app from the command line is very likely going to repair it, and there’s no reason why it would result in data loss. It’s safe to use.