I had to change and reload the configuration a couple of times for troubleshooting Siteground mail service. There are multiple bits of advice on how to do it most quickly. Summarizing all of them leaves confusion. So, could you tell me the differences between the commands listed below in more deta…

I going to do a PR on GitHub but I need to understand each command in detail what is currently not the case. Could you tell me, what each command triggers? I’ve read many posts in this regard but the information is not consistence. A good example is start. Once it is said it is just used to stop a…

Initialize means that if no container exists it will be created. If you stop and start, you’ll stop and start the same container with the same parameters (like smtp and other env settings), but if you destroy first, a new container with new env settings will be created, or initialized.

what is the difference between bootstrap and start if no container exits?

Bootstrap builds a new docker image,which is necessary to be able to “initialize” a running container. Rebuild will always work. Sometimes it’s unnecessary, as a destroy and start is enough to make env settings (like smtp) take effect. But lots of people won’t really understand these intricacies, s…

so ./discourse-setup is the least invasive command as it only recreates discourse’s software. Bootstrap from very scratch, begins with docker image start, from scratch, builds a container ./discourse-setup, runs discourse’s setup what command is available to reapply config as defined in app…

If you need to know what each command does exactly you can read it here: discourse_docker/launcher at master · discourse/discourse_docker · GitHub

thanks that helps :slight_smile: There is once mentioned setup , is it related to ./discourse-setup?

This is a bit more complete now: Usage: launcher COMMAND CONFIG [--skip-prereqs] [--docker-args STRING] Commands: start: Start/initialize a container stop: Stop a running container restart: Restart a container destroy: Stop and remove a container enter: …

El comando del lanzador en la carpeta /var/discourse no es autoexplicativo

Soporte Instalación

sam (Sam Saffron) 21 Agosto, 2019 04:10 2

I am not sure I am following here… can you make a PR with your proposed change?

1 me gusta

Tema		Respuestas	Vistas
Can't get discourse working again Self-hosting	8	1741	16 Febrero 2020
What's the different between rebuild and bootstrap Self-hosting	13	5358	23 Mayo 2023
Don't forget to run docker remove app when reinstalling discourse Support	2	91	14 Enero 2025
No web_only.yml Self-hosting	4	50	10 Octubre 2024
Container restart - discourse tries to reinstall Self-hosting unsupported-install	24	2920	30 Julio 2020

El comando del lanzador en la carpeta /var/discourse no es autoexplicativo

Temas relacionados