!BIDAeUqYWNCjRLhRdj:matrix.org

#dendrite-dev:matrix.org

589 Members
Dendrite developer discussion | Help out! https://github.com/matrix-org/dendrite/blob/master/docs/CONTRIBUTING.md270 Servers

Load older messages


SenderMessageTime
7 Dec 2021
@_neb_github_=40neilalexander=3amatrix.org:matrix.orgGithub [@neilalexander:matrix.org] [matrix-org/dendrite] MFAshby synchronize pull request #2060: Added std type to logging config. [open] - https://github.com/matrix-org/dendrite/pull/2060 11:53:51
@_neb_github_=40neilalexander=3amatrix.org:matrix.orgGithub [@neilalexander:matrix.org] [matrix-org/dendrite] MFAshby synchronize pull request #2060: Added std type to logging config. [open] - https://github.com/matrix-org/dendrite/pull/2060 13:47:01
@bn4t_:matrix.orgbn4t_ joined the room.14:36:11
@bn4t_:matrix.orgbn4t_ set a profile picture.14:36:28
8 Dec 2021
@jsalter:matrix.orgJames [away] changed their display name from James [AEDT +11] to James [away].01:30:57
@_neb_github_=40neilalexander=3amatrix.org:matrix.orgGithub [@neilalexander:matrix.org] [matrix-org/dendrite] bn4t opened pull request #2070: Don't ignore config flag for yggdrasil demo if set [open] - https://github.com/matrix-org/dendrite/pull/2070 09:00:29
@_neb_github_=40neilalexander=3amatrix.org:matrix.orgGithub [@neilalexander:matrix.org] [matrix-org/dendrite] bn4t synchronize pull request #2070: Don't ignore config flag for yggdrasil demo if set [open] - https://github.com/matrix-org/dendrite/pull/2070 09:11:35
9 Dec 2021
@_neb_github_=40neilalexander=3amatrix.org:matrix.orgGithub [@neilalexander:matrix.org] [matrix-org/dendrite] neilalexander opened pull request #2071: Return event NID from `StoreEvent`, match PSQL vs SQLite behaviour, tweak backfill persistence [open] - https://github.com/matrix-org/dendrite/pull/2071 13:53:43
@_neb_github_=40neilalexander=3amatrix.org:matrix.orgGithub [@neilalexander:matrix.org] [matrix-org/dendrite] neilalexander review_requested pull request #2071: Return event NID from `StoreEvent`, match PSQL vs SQLite behaviour, tweak backfill persistence [open] - https://github.com/matrix-org/dendrite/pull/2071 13:53:44
@_neb_github_=40neilalexander=3amatrix.org:matrix.orgGithub [@neilalexander:matrix.org] [matrix-org/dendrite] neilalexander closed pull request #2071: Return event NID from `StoreEvent`, match PSQL vs SQLite behaviour, tweak backfill persistence [closed] - https://github.com/matrix-org/dendrite/pull/2071 15:03:28
10 Dec 2021
@jsalter:matrix.orgJames [away] left the room.03:32:58
@rhymefororange:zlol.lg.uarhymefororange Hi everyone. I'm new to dendrite and would like to start contributing. I tried to follow the instructions for docker monolith deployment, but when I start the monolith container I get this error:
docker-monolith-1 | time="2021-12-10T13:13:43.298170403Z" level=panic msg="failed to start kafka consumer" func="setupKafka\n\t" file=" [kafka.go:27]" error="kafka: client has run out of available brokers to talk to (Is your cluster reachable?)"
I looked into the docker compose file and it turns out running
docker-compose -f docker-compose.deps.yml up
instead of
docker-compose -f docker-compose.deps.yml up postgres
fixes the problem, because it starts the kafka container that the consumers are looking for.
Is that a bug in the docs or am I missing something?
13:19:04
@rhymefororange:zlol.lg.uarhymefororange * Hi everyone. I'm new to dendrite and would like to start contributing. I tried to follow the instructions for docker monolith deployment, but when I start the monolith container I get this error:
docker-monolith-1 | time="2021-12-10T13:13:43.298170403Z" level=panic msg="failed to start kafka consumer" func="setupKafka\n\t" file=" [kafka.go:27]" error="kafka: client has run out of available brokers to talk to (Is your cluster reachable?)"
I looked into the docker compose file and it turns out running
docker-compose -f docker-compose.deps.yml up
instead of
docker-compose -f docker-compose.deps.yml up postgres
fixes the problem, because it starts the kafka container that the consumers are looking for.
Is that a bug in the docs or am I missing something?
13:19:24
@neilalexander:matrix.orgneilalexander
In reply to @rhymefororange:zlol.lg.ua
Hi everyone. I'm new to dendrite and would like to start contributing. I tried to follow the instructions for docker monolith deployment, but when I start the monolith container I get this error:
docker-monolith-1 | time="2021-12-10T13:13:43.298170403Z" level=panic msg="failed to start kafka consumer" func="setupKafka\n\t" file=" [kafka.go:27]" error="kafka: client has run out of available brokers to talk to (Is your cluster reachable?)"
I looked into the docker compose file and it turns out running
docker-compose -f docker-compose.deps.yml up
instead of
docker-compose -f docker-compose.deps.yml up postgres
fixes the problem, because it starts the kafka container that the consumers are looking for.
Is that a bug in the docs or am I missing something?
You probably want to run a monolith Dendrite deployment, make sure that use_naffka is set in your Dendrite config and then forego running Kafka altogether
13:31:24
@rhymefororange:zlol.lg.uarhymefororange
In reply to @neilalexander:matrix.org
You probably want to run a monolith Dendrite deployment, make sure that use_naffka is set in your Dendrite config and then forego running Kafka altogether
Yep, that is what I missed, thanks. I used dendrite-config.yaml from build/docker/config where use_naffka is set to false instead of using dendrite-config.yaml from root of the project.
13:49:13
@_neb_github_=40neilalexander=3amatrix.org:matrix.orgGithub [@neilalexander:matrix.org] [matrix-org/dendrite] PiotrKozimor synchronize pull request #1842: Implement Pushers API [open] to danpe - https://github.com/matrix-org/dendrite/pull/1842 13:53:56
@neilalexander:matrix.orgneilalexander I think the one in build/docker/config is just prepopulated with database connection strings and paths that make sense for Docker 13:58:38
@neilalexander:matrix.orgneilalexander * I think the one in build/docker/config is just prepopulated with database connection strings and paths that make sense for Docker+PSQL 13:58:42
@rhymefororange:zlol.lg.uarhymefororangeBut now I have a different problem. When I point element to https://localhost:8448 it says that this does not apper to abe a valid homeserver address and I see docker-monolith-1 | 2021/12/10 13:47:42 http: TLS handshake error from 172.21.0.1:48812: remote error: tls: bad certificate in the logs. I generated the certificates and placed them in build/docker (which is where I launch the containers from) and build/docker/config (which is mounted in the container AFAIK). Am I missing something again? plaintext http://localhost:8008 works fine14:39:40
@rhymefororange:zlol.lg.uarhymefororange * But now I have a different problem. When I point element to https://localhost:8448 it says that this does not apper to be a valid homeserver address and I see docker-monolith-1 | 2021/12/10 13:47:42 http: TLS handshake error from 172.21.0.1:48812: remote error: tls: bad certificate in the logs. I generated the certificates and placed them in build/docker (which is where I launch the containers from) and build/docker/config (which is mounted in the container AFAIK). Am I missing something again? plaintext http://localhost:8008 works fine14:39:51
@rhymefororange:zlol.lg.uarhymefororange * But now I have a different problem. When I point element to https://localhost:8448 it says that this does not apper to be a valid homeserver address and I see
docker-monolith-1 | 2021/12/10 13:47:42 http: TLS handshake error from 172.21.0.1:48812: remote error: tls: bad certificate
in the logs. I generated the certificates and placed them in build/docker (which is where I launch the containers from) and build/docker/config (which is mounted in the container AFAIK).
Am I missing something again? plaintext http://localhost:8008 works fine
14:39:58
@rhymefororange:zlol.lg.uarhymefororange * But now I have a different problem. When I point element to https://localhost:8448 it says that this does not apper to be a valid homeserver address and I see
docker-monolith-1 | 2021/12/10 13:47:42 http: TLS handshake error from 172.21.0.1:48812: remote error: tls: bad certificate
in the logs. I generated the certificates and placed them in build/docker (which is where I launch the containers from) and build/docker/config (which is mounted in the container AFAIK).
Am I missing something again? plaintext http://localhost:8008 works fine
14:40:33
@neilalexander:matrix.orgneilalexanderUnless those certificates came from a signed authority then they will not pass client validation checks, which is normal14:48:29
@neilalexander:matrix.orgneilalexander... but if you just want to talk to the HS for development purposes then using plain HTTP on port 8008 would be fine14:48:40
@rhymefororange:zlol.lg.uarhymefororangeOk. I thought I could deploy locally with self-signed certificates and use it that way even if the browser tells me it if insecure and I have to accept it. 14:56:43
@rhymefororange:zlol.lg.uarhymefororange * Ok. I thought I could deploy locally with self-signed certificates and use it that way even if the clients tells me it if insecure and I have to accept it. 14:57:44
@rhymefororange:zlol.lg.uarhymefororangeSo only the CA-issued certs are going to work with matrix clients because they do the validation, right?14:58:14
@rhymefororange:zlol.lg.uarhymefororange * Ok. I thought I could deploy locally with self-signed certificates and use it that way even if the client tells me it if insecure and I have to accept it. 14:58:36
@rhymefororange:zlol.lg.uarhymefororange * Ok. I thought I could deploy locally with self-signed certificates and use it that way even if the client tells me it is insecure and I have to accept it. 14:58:42
@neilalexander:matrix.orgneilalexanderUnless the client has a switch to not validate the certificates, yep15:02:23

There are no newer messages yet.


Back to Room ListRoom Version: 9