ÉCHEC lors de la tentative d'installation du plugin

Salut :wave:
J’utilise la dernière version de Discourse et j’ai cette erreur lorsque j’essaie d’installer un plugin : GitHub - discourse/discourse-encrypt: A plugin that provides a secure communication channel through Discourse.
Comment corriger l’erreur pour installer le plugin ?

--- Pile d'appels JS ---

ERREUR FATALE : Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0xb00e10 node::Abort() [ember]
 2: 0xa1823b node::FatalError(char const*, char const*) [ember]
 3: 0xcee09e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [ember]
 4: 0xcee417 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [ember]
 5: 0xea65d5  [ember]
 6: 0xea70b6  [ember]
 7: 0xeb4fee  [ember]
 8: 0xeb5a30 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [ember]
 9: 0xeb89ae v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [ember]
10: 0xe79b12 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [ember]
11: 0xe7443c v8::internal::FactoryBase<v8::internal::Factory>::AllocateRawArray(int, v8::internal::AllocationType) [ember]
12: 0xe74515 v8::internal::FactoryBase<v8::internal::Factory>::NewFixedArrayWithFiller(v8::internal::Handle<v8::internal::Map>, int, v8::internal::Handle<v8::internal::Oddball>, v8::internal::AllocationType) [ember]
13: 0x10d2afd v8::internal::Handle<v8::internal::NumberDictionary> v8::internal::HashTable<v8::internal::NumberDictionary, v8::internal::NumberDictionaryShape>::New<v8::internal::Isolate>(v8::internal::Isolate*, int, v8::internal::AllocationType, v8::internal::MinimumCapacity) [ember]
14: 0xd53916 v8::internal::Builtin_ArrayConcat(int, unsigned long*, v8::internal::Isolate*) [ember]
15: 0x15e7dd9  [ember]
Aborted (core dumped)
error Command failed with exit code 134.
Error running ember build
I, [2022-02-07T04:26:54.469601 #1]  INFO -- : yarn run v1.22.17
$ /var/www/discourse/app/assets/javascripts/node_modules/.bin/ember build -prod
WARNING: Node v16.13.2 is not tested against Ember CLI on your platform. We recommend that you use the most-recent "Active LTS" version of Node.js. See https://git.io/v7S5n for details.
DEPRECATION: The integration of jQuery into Ember has been deprecated and will be removed with Ember 4.0. You can either opt-out of using jQuery, or install the `@ember/jquery` addon to provide the jQuery integration. Please consult the deprecation guide for further details: https://emberjs.com/deprecations/v3.x#toc_jquery-apis
Environment: production
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I, [2022-02-07T04:26:54.503554 #1]  INFO -- : Terminating async processes
I, [2022-02-07T04:26:54.505728 #1]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 42
I, [2022-02-07T04:26:54.508010 #1]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 103
103:signal-handler (1644208014) Received SIGTERM scheduling shutdown...
2022-02-07 04:26:54.510 UTC [42] LOG:  received fast shutdown request
2022-02-07 04:26:54.517 UTC [42] LOG:  aborting any active transactions
2022-02-07 04:26:54.532 UTC [42] LOG:  background worker "logical replication launcher" (PID 51) exited with exit code 1
2022-02-07 04:26:54.534 UTC [46] LOG:  shutting down
103:M 07 Feb 2022 04:26:54.565 # User requested shutdown...
103:M 07 Feb 2022 04:26:54.565 * Saving the final RDB snapshot before exiting.
2022-02-07 04:26:54.569 UTC [42] LOG:  database system is shut down
103:M 07 Feb 2022 04:26:54.678 * DB saved on disk
103:M 07 Feb 2022 04:26:54.678 # Redis is now ready to exit, bye bye...

FAILED
--------------------
Pups::ExecError: cd /var/www/discourse &amp;&amp; su discourse -c 'bundle exec rake themes:update assets:precompile' failed with return #<Process::Status: pid 1116 exit 1>
Location of failure: /usr/local/lib/ruby/gems/2.7.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"assets_precompile", "cmd"=>["su discourse -c 'bundle exec rake themes:update assets:precompile'"]}
a1604b58388b06dbcfbad098806d3fece924a8fdef43e77cd037d5cc3f65fdb3
** 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.

Avez-vous activé HTTPS avant d’installer ce plugin ?

Oui, bien sûr, je l’ai installé en suivant cette instruction : https://github.com/discourse/discourse/blob/main/docs/install-cloud.md

Combien de mémoire et de swap avez-vous ?

Comment le savoir ? Je connais très mal les commandes du terminal pour Docker.
Mon serveur est Ubuntu 20.04, 1024 Mo, 1 CPU

Ceci.

Cela pourrait ne pas être suffisant de nos jours. Essayez de le redimensionner à quelque chose de plus grand. Si vous ne redimensionnez pas le disque, vous pourrez toujours le réduire après la reconstruction (en supposant une plateforme comme DigitalOcean).

J’ai essayé de lancer un nouveau site de test sur une gouttelette DO de 1 Go hier, et cela a rencontré la même erreur. Le redimensionnement à 2 Go et la nouvelle tentative ont fonctionné pour moi. :+1:

Merci !

Peut-être que Discourse supprimera cette ligne dans les instructions d’installation.

Parce que Discourse a cette erreur s’il fonctionne avec 1 Go de RAM.

La valeur par défaut de 1 Go de RAM fonctionne bien pour les petites communautés Discourse. Nous recommandons 2 Go de RAM pour les communautés plus importantes.

Avez-vous un espace d’échange (swap) fonctionnel de 2 Go sur ce serveur de 1 Go ?

@RedBear essaie de reconstruire maintenant