The site maintenance with “./launcher rebuild app” takes some time to fully rebuild the site (installing new plugins etc from git). Is there any recommended way to show a static page saying “Under maintenance” while I rebuild the discourse? What I thought was to use nginx. That involves stopping the docker to serve on port 80 and letting nginx reverse proxy to takeover and redirect traffic to either docker container or to my static page. I’m thinking of doing that with manually editing the nginx.conf to the following whenever needed, server { listen 80; server_name your-discourse-domain.com; location / { proxy_pass http://localhost:80; proxy_set_header Host $http_host; proxy_http_version 1.1; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto https; proxy_redirect http:// https://; } } and replacing with, server { listen 80; server_name your-discourse-domain.com; location / { root /path/to/your/maintenance/page; } } What are your suggestions? I’m using AWS EC2 servers. Is there any better way?

Hi @PrettyGirl There is, yes. Take a look here: [imagem] Add an offline page to display when Discourse is rebuilding or starting up Sysadmins warning 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 lose 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 …

The way I think is better and easier is to use a two container setup so you can build a new container while the old one runs. There is much less down time that way. Others think that running an extra web server is easier.

That will work in a lot of cases, but is still going to experience downtime whenever the data container needs to be updated.

Major database upgrades happen less than once a year. Minor database upgrades don’t take very long and you can rebuild the data container, destroy and start the web container in a very few minutes. It seems that some people would rather have a pretty message saying that the site is down rather than reducing down time, so a second container is the way to do it. Actually, maybe the easiest solution would be to just have a second nginx container with a “back soon” message that you ran by hand while doing an upgrade, like ./launcher stop app docker run nginx --name back-soon # and some more stuff to see that a page was served ./launcher bootstrap app ./launcher destroy app docker stop back-soon ./launcher start app But then you have to get a cert and keep the cert updated for the back-soon container, which is complicated. EDIT: Here is the canonical topic for this discussion Add an offline page to display when Discourse is rebuilding or starting up - #83 by amotl

Exibindo uma página "Em manutenção" usando nginx no "launcher rebuild app"?

Suporte ao Produto Instalação

Stephen (Stephen) 8 Outubro , 2023 02:40 2

Olá @PrettyGirl

Sim, existe. Dê uma olhada aqui:

Tópico		Respostas	Vistas
Display static error page while site is down Product Support	9	858	11 Setembro , 2022
Maintenance page while docker takes time to rebuilt Self-hosting	4	806	3 Abril , 2023
Nginx: How to show a placeholder while updating? Product Support	1	1038	26 Dezembro , 2018
Site maintenance mode during rebuilds? Feature	7	5361	17 Outubro , 2016
Is there a way to display a banner when the server is updating Product Support	4	979	22 Abril , 2022

Exibindo uma página "Em manutenção" usando nginx no "launcher rebuild app"?

Related topics