mirror of
https://github.com/1f349/dendrite.git
synced 2024-09-20 02:46:34 +01:00
7cde99a7a7
Currently, the documentation makes use of the old names for the binary and configuration files. This updates the documentation so that users can follow the guide without issues again. These changes don't require any go unit tests because it does not modify any golang code. Signed-off-by: `Robin Westerik <gh@westerik.me>`
43 lines
1.2 KiB
Markdown
43 lines
1.2 KiB
Markdown
---
|
|
title: Starting the monolith
|
|
parent: Installation
|
|
has_toc: true
|
|
nav_order: 9
|
|
permalink: /installation/start/monolith
|
|
---
|
|
|
|
# Starting the monolith
|
|
|
|
Once you have completed all of the preparation and installation steps,
|
|
you can start your Dendrite monolith deployment by starting `dendrite`:
|
|
|
|
```bash
|
|
./dendrite -config /path/to/dendrite.yaml
|
|
```
|
|
|
|
By default, Dendrite will listen HTTP on port 8008. If you want to change the addresses
|
|
or ports that Dendrite listens on, you can use the `-http-bind-address` and
|
|
`-https-bind-address` command line arguments:
|
|
|
|
```bash
|
|
./dendrite -config /path/to/dendrite.yaml \
|
|
-http-bind-address 1.2.3.4:12345 \
|
|
-https-bind-address 1.2.3.4:54321
|
|
```
|
|
|
|
## Running under systemd
|
|
|
|
A common deployment pattern is to run the monolith under systemd. For this, you
|
|
will need to create a service unit file. An example service unit file is available
|
|
in the [GitHub repository](https://github.com/matrix-org/dendrite/blob/main/docs/systemd/monolith-example.service).
|
|
|
|
Once you have installed the service unit, you can notify systemd, enable and start
|
|
the service:
|
|
|
|
```bash
|
|
systemctl daemon-reload
|
|
systemctl enable dendrite
|
|
systemctl start dendrite
|
|
journalctl -fu dendrite
|
|
```
|