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 detail?
The information in install guide and posts in this forum are somehow inconsistent. It isn’t fully clear what e.g. is the difference between initializing and building a container.
There should be a ladder of escalation telling what actions requires what command if you change e.g. app.yml as some tell start is enough other say you have to rebuild or do also ./discourse-setup
Commands:
start: Start/initialize a container
stop: Stop a running container
restart: Restart a container
destroy: Stop and remove a container
bootstrap: Bootstrap a container for the config based on a template
rebuild: Rebuild a container (destroy old, bootstrap, start new)
I’m slowly building up the impression that all the commands are a follow-up sequence of actions.
Each successive step/command does the same as it pre-successor plus something extra.
for example something like this
start-up
bootstrap: destroy old + Bootstrap a container for the config based on a template
rebuild: bootstrap + Rebuild a container (start new), meaning it does things like downloading the latest versions of software and implementing updated config
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 and start the container if e.g. doing something on the host. In another topic it is mentioned that it initializes a container, whatever initialize means
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.
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, so it’s better to just tell them to always rebuild because it always works.
