האם שדרוג תקין במצב קריאה בלבד, ומדוע מצב קריאה בלבד דורש הפעלת שחזורים?

סיכום מבוסס בינה מלאכותית

peternlewis plans to perform server maintenance, including upgrading the OS and Discourse to 2.8.0, and intends to use read-only mode during this time. They note the odd placement of the read-only toggle under Backup settings and question why enabling restores is required to activate read-only mode, pointing out that read-only may be needed for reasons beyond backups. pfaffman advises against upgrading the OS in-place, recommending instead spinning up a new VM to minimize downtime and avoid risk of breaking the forum. They acknowledge the placement of read-only mode under backups is unusual, but suggest it’s typically used just before migrating to a new server — hence its association with restore functionality.

I plan to do some maintenance to the server, including updating the server and the server OS, as well as updating Discourse to 2.8.0 from 2.7.x. So I want to set it in to read-only mode for the duration of that process.

I saw the method is oddly in the Backups settings as described:

Firstly, I presume read-only mode does not affect an upgrade process?

Also, it is really weird that Enable read-only is in the Backup settings, and even more weird that it requires restoring to be enabled in order to set the site in to read-only mode. There are other reasons for wanting to set a site in to read-only mode.

Thanks.

If your plan is to upgrade the OS, I’d recommending instead that you spin up a new VM and move to it. Down time will be much less and there is zero chance of ending up with a broken forum.

It is a little strange that read-only is on the backup page, but the time that most people put a forum in read-only mode is just before making a backup to move to a different server.