The name of the file (and hence the name you give to launcher). That is the resulting name of the container which is run, the directory in which the persistent data for the application is stored, and so forth.
The database name defaults to
discourse, but you can change that by adding the following in the
params section of the
.yml file you create:
So it’d look like this:
You can either run the database in the same container as the web application, or you can run the database in a separate container or on the server itself. The
standalone.yml template in the
samples directory is an all-in-one setup, while the combination of the
data.yml templates will give you separate containers for the web application and datastores. You could also configure the
web_only.yml to connect to existing, standalone PostgreSQL and Redis servers, if you felt so inclined.
The second instance will use another name, as long as you configure it to do so, as described previously.