Comment reconstruire Discourse sans changer de version ?

Soutien Installation
1

I need to update the smtp settings in app.yml, but I do not want to change the version of discourse.

When I specify a version via the version tag, the rebuild fails with the error below. I am currently on version 2.4.0.beta8.

FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && find /var/www/discourse ! -user discourse -exec chown discourse {} \+ failed with return #<Process::Status: pid 336 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"web", "cmd"=>["gem update bundler", "find $home ! -user discourse -exec chown discourse {} \\+"]}
6269af00c2a4671a6fd2cb13a55bd475743205262bae7f483bf468e4dcacbeed
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
1 « J'aime »
2

This comes up every year and probably should have a howto topic. I just searched for specific version:

1 « J'aime »
3

Yes, difference here is that i am using the version tag in the yml, but get an error when rebuilding

1 « J'aime »
4

If you just need to change smtp settings you can

./launcher destroy app 
./launcher start app
5 « J'aime »
5

ok, so that will read the yml even if it does not rebuild, sounds good. While that will fix my urgent issue, i am still intrested in why version does not work.

6

You said that you get “an error”. That means that you did something wrong. My best guess is a YML formatting error, but without knowing what the error was, there is really no way to know.

Sorry, “please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.”

3 « J'aime »
7

Yes, I can see that the information i gave in the post was not detailed enough. I do not think it is a formatting error, since the yml works fine without the version tag.

I tested some more, and it seems like whatever bug I encountered does not trigger in version 10 and 11, but does trigger in version 4 to 9.

I can only find two errors in the print, and i think they are expected:

2020-02-22 10:42:33.410 UTC [62] postgres@postgres ERROR:  database "discourse" already exists

2020-02-22 10:42:33.533 UTC [73] postgres@discourse ERROR:  role "discourse" already exists

I looked at the release notes for version 10, and did not find a reference to a fix related to this.

Its good that it is fixed, and with your work around for the smpt settings (will test it on monday, dont want to mess with the production server during the weekend) there is no urgent need from me, but it would be good to know if there is an unknown error that the tests will not catch, and that may return, if it was ‘fixed’ by accident and not by a targeted change. I guess i want to know how stable the version function can be expected to be in the future.

This is a dump of the output from a run with v2.4.0.beta9 as target version.
dump_disco_version_error.txt (127.5 KB)

8

I finally found time to test this, and it did not work. I can see that it prints the correct pw when the app starts, but emails still fail due to access denied.

9

Hmm. I’m sure that it used to work. I have seen some other settings not get pushed to the config file. I’m not sure if it’s considered a bug.

10

It could also be that I am using an old version, so it may or may not work in the latest version. I just wanted to update with my findings.

11

J’ai eu besoin de revenir là-dessus : il me semble que la version fonctionne pour les branches, mais pas pour les tags. Je suppose que c’est parce que le lanceur ne récupère pas tous les tags d’abord, mais je ne sais pas. Y a-t-il un moyen de modifier les scripts du lanceur ?

12

J’ai enfin compris ce qui ne va pas : les dépôts discourse_docker et discourse dépendent l’un de l’autre, si bien qu’une version spécifique de Discourse ne peut être installée qu’avec une version spécifique du dépôt discourse_docker. Malheureusement, il n’y a pas de balises dans le dépôt discourse_docker, ce qui rend difficile la détermination du SHA à utiliser pour installer une version donnée. C’est au moins rassurant d’avoir une conclusion. Je vais commencer à prendre des notes à ce sujet pour les installations que je ferai à l’avenir.

1 « J'aime »