Hi, when one is in the container in the console, how can one restart Discourse?

Why can’t you restart it from the Discourse directory? The script to do this job is intended to be run from there.

If I do it this way, all the changes I have made to files in the container will be reset when the whole container is restarted…

Your changes will persist if you make them properly: with variables in app.yml with a Theme or Theme Component with a Plugin (if you need to change the behaviour of the back end for example) to the database (preferably via the front end or a rake task) uploads

When I edit the app.yml, I have to rebuild

Not for everything. Some variable changes will apply on a simple restart via the launcher eg SMTP creds I believe. ./launcher restart app

No, the values are the old ones, although I restarted after editing the YML

Which variables? For sure for many variables you will need to rebuild. Rebuilding is normal. Embrace it :).

Well you shouldn’t need to rebuild more than once a week? And even then I would use the upgrade page most often to eliminate significant downtime.

yupz. it just take time 15min-30min if you configuration the file app.yml after edit you must ./launcher rebuild app or you can use this command ./launcher rebuild app --skip-prereqs

Discourse im Container neu starten

Unterstützung Installation

merefield (Robert) 5. Mai 2023 um 14:34 2

Warum können Sie es nicht vom Discourse-Verzeichnis aus neu starten? Das Skript, das diese Aufgabe erledigt, ist dafür vorgesehen, von dort aus ausgeführt zu werden.

Thema		Antworten	Aufrufe
How to reload configuration after app.yml changes? Self-hosting	7	8869	3. April 2018
Does ./launcher rebuild keep all settings & posts? Support	3	9509	16. November 2015
My forum goes down when I do launcher rebuild app Self-hosting	15	2031	23. Oktober 2022
Do I need to rebuild when my domain name changes? Support	8	1737	31. März 2017
Moving the server Self-hosting	8	532	1. Februar 2024

Discourse im Container neu starten

Verwandte Themen