Depends on the system, but
shutdown -r now should get you there. If it complains that you must be the superuser or that it can’t find the command, run
sudo reboot or
sudo shutdown -r now instead.
By the way, a few quick tips:
- When you start a SSH session, you always get a new, freshly started shell. (Shells are programs that read and parse your commands.)
- Each process, including the shell, has its own current working directory. You can type
pwd in the shell to see the full name of the directory the shell is currently in, and you can type
cd followed by a name to change the shell’s current directory.
- Names that begin with a slash are absolute.
/tmp always refers to the same directory, no matter what the current working directory is.
/ is called the root directory. Any name that doesn’t start with a slash, including for example
./, is relative to the current working directory.
. alone is synonymous for the current directory;
.. is the current directory’s parent.
/.. exists, but is always identical to
- Linux allows you to run a process in a “container” by changing its root directory. For example, Discourse runs inside such a container: its files are actually stored somewhere in
/var/lib/docker/, and the Docker program tricks Discourse into believing otherwise.
Discourse cannot actually read your
app.yml, it simply has no way to refer to the file. Instead the
launcher script goes through the configuration file, injects your settings into Discourse’s container and then restarts Discourse.
So yes – you need to rebuild the container after every “major” configuration change; if you only change the
env sections, a simple restart instead of a rebuild will do.