Si tengo una copia de discourse_docker en la revisión A, ejecuto launcher bootstrap web_only seguido de launcher run web_only en el momento T1, y luego, en el momento T2, ejecuto los mismos comandos exactos, ¿obtendré exactamente el mismo software en ejecución en T1 que en T2?
Es decir, ¿el ID del commit de discourse_docker más cualquier estado presente en los archivos YAML constituye el estado completo que genera el artefacto en ejecución?
Sospecho que no es así, ya que parece que Discourse extrae de los remotos de git durante la compilación y el inicio, pero solo quiero verificarlo con la comunidad.
It depends on what branch you are pulling. If it’s tests-passed, then you are likely to get a different version at every rebuild /bootstrap. You could or either a beta version or a commit id there to see that things stay the same.
If you want paid support to get your larger problem solved and have a budget, my contact info is in my profile.
thanks @pfaffman . Quick clarification. By branch do you mean the branch of discourse_docker or is there another setting that can lock the main discourse to a certain branch? Just to be clear, in my example, I am not deliberately pulling new code for either discourse_docker or discourse . I’m getting the feeling that discourse_docker does either one, or both behind the scenes. Ideally I would want to disable this behaviour so I can get a repeatable build. Is this possible?
Launcher will pull the version of Discourse specified by the params: version: key in web_only.yml. As described in that file, the default is tests-passed.
In addition, plugins will normally update unless you pin a version in their git clone.