Update in browser vs Terminal

[merefield (Robert)]

@alltiagocom

Technologically speaking, do you think this will eventually change one day where we can do everything in the browser? I don’t know the technicalities of this process, that’s why I’m asking.

I suspect it will always be like this on the standard install.

You can find resources on here to configure a “we’re offline, come back later screen” to mitigate those 20 minutes, but it’s not the standard install and I would suggest you keep things simple and easily supported.

Add an offline page to display when Discourse is rebuilding or starting up

This guide is intended for advanced users, who are already using nginx outside the docker container. By following this guide you make your setup more complicated and will loose some speed benefits like HTTP2 if you’re not running Ubuntu 16.04 or later. Proceed with caution! When Discourse is rebuilding or starting up, your users will usually either see an error message from their browser… [image] …or a not-so-nice 502 error message from Nginx: [image] If you’re a perfectionist l…