Restart Discourse in Container

Installation
1

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

2

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

1 Like
3

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…

4

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
1 Like
5

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

6

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

./launcher restart app

1 Like
7

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

8

Which variables?

For sure for many variables you will need to rebuild.

Rebuilding is normal. Embrace it :).

1 Like
9

Rebuilding just takes too long

10

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.

1 Like
11

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