Bonjour, A recent commit in docker_discourse breaks the ability to specify a tag (for instance v2.6.0) in the version: value of app.yml. This is useful to install older versions of discourse , for test purposes. The problem shows like this when specifying version: v2.6.0 when using e2eb085714dfcf2a…

Thanks for clarifying: that’s exactly the part I was missing. For those who are confused in the same way I was, getting a release tag of discourse can be done by: Making sure the version parameter is not set in app.yml, for instance:params: db_default_text_search_config: "pg_catalog.english" #…

I would not call this a bug per-se, but we want to offer some sort of instructions on how to get ancient versions of discourse installed even if it involves a more complicated template or something. @Falco is investigating.

[afbeelding] dachary: A recent commit in docker_discourse breaks the ability to specify a tag (for instance v2.6.0) in the version: I agree the depth should be configurable, perhaps via an environmental variable, defaulting to “shallow”; but configurable with a simple environmental.

I think the problem here is that the tags are not known locally when doing the checkout, like in the following (non discourse related) issue: What is git tag, How to create tags & How to checkout git remote tag(s) git, git-checkout, git-tag, git-refspec asked by …

[afbeelding] lucasbasquerotto: Running git fetch --all should solve the problem, but I don’t know how much it could increase the image size (unless another instruction clears the unused references later on). That doubles the repository size :slightly_frowning_face: [afbeelding] lucasbasqu…

[afbeelding] Falco: Problem is that at the image build time I don’t know what branch you will want in the future. You’re right, at that time we don’t know the version, it seems the base image uses the current version + tests-passed branch, although the branch will have the commit at the time …

[afbeelding] lucasbasquerotto: When git pull is called, the entire repository is pulled , and can take several minutes, because only a shallow clone was done before. You can try running just the above instructions locally and see. Are you sure about that? ➜ discoursesmall git:(6a42acbf) doc…

@lucasbasquerotto you are correct to point out that the git pull is not strictly necessary though, we’ve removed it here This should allow other branches (or forks) to play a little nicer with discourse_docker moving forward :slight_smile:

Yes, I see that it does a fetch and then a checkout in the correct branch after the pull, so I think the git pull is not necessary (I haven’t tested tough). For tags it seems that I still need to fetch the tag separately, but it seems doable, furthermore the branches are more commonly used, so the …

Is it safe to assume that the version option in configuration file standalone.yml has no effect? samples/standalone.yml d9f2f312c db_default_text_search_config: "pg_catalog.english" ## Set db_shared_buffers to a max of 25% of the total …

It still has an effect, but it can only be set to branches now.

Ondiepe git fetch regressie in discourse_docker

Ondersteuning

Falco (Falco) 31 december 2020 om 16:02 15

Try adding the mentioned key and using an older image from discourse/base - Docker Image

Topic		Antwoorden	Weergaven
Help deploying older versions of Discourse Self-hosting	22	341	30 maart 2026
Can't change repo in discourse docker Development	9	3525	15 februari 2018
Build failed for specific commit hash Self-hosting	8	723	12 april 2023
First installation - Error on rebuild app Self-hosting	8	416	15 februari 2024
Tag 1.3.10 not found on reload Support	6	1331	17 januari 2017

Ondiepe git fetch regressie in discourse_docker

Gerelateerde topics