![]() # HTTP basic authentication to protect access to monitoring. # Whether or not Prometheus metrics are enabled. # Configuration for Prometheus metric collection. # mode, but means that you can run a single-process server without requiring # Whether to use Naffka instead of Kafka. # you are running more than one Dendrite homeserver on the same Kafka deployment. # The prefix to use for Kafka topic names for this homeserver. # List of Kafka broker addresses to connect to. # party identifiers such as phone numbers and email addresses. # Lists of domains that the server will trust as identity servers to verify third # servers for our key but increases the period that a compromised key will be Increasing this number will reduce the number of requests made by other # How long a remote server can cache our server signing key before requesting it # provided to any other homeserver that asks when trying to verify old events. # keys will not be used for federation request or event signing, but will be # to old signing private keys that were formerly in use on this domain. # The paths and expiry timestamps (as a UNIX timestamp in millisecond precision) Private_key: /etc/dendrite/matrix_key.pem # The path to the signing private key file, used to sign requests and events. This configuration applies to all components. # connection can be idle in seconds - a negative value is unlimited. # "conn_max_lifetime" option controls the maximum length of time a database # engine default, and a negative value will use unlimited connections. # number of open/idle database connections. # The "max_open_conns" and "max_idle_conns" settings configure the maximum # small number of users and likely will perform worse still with a higher volume # SQLite is typically around 20-30% slower than PostgreSQL when tested with a # PostgreSQL is significantly better and recommended for multi-user deployments. # needed for the database when using SQLite mode. # PostgreSQL: SQLite is embedded into Dendrite and therefore no further prerequisites are # Each component with a "database" section can accept the following formats # database "connection_string" line in each component section is correct. # "global" section for your deployment, and you will need to check that the # At a minimum, to get started, you will need to update the settings in the # configuration section, in addition to the "global" section which applies to # The configuration is split up into sections - each Dendrite component has a # This is the Dendrite configuration file. Sudo /opt/dendrite/bin/generate-keys -private-key /etc/dendrite/matrix_key.pem Sudo chown -R dendrite:dendrite /var/log/dendrite Sudo chown -R dendrite:dendrite /opt/dendrite Go build -o bin/dendrite-monolith-server. Logout
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |