![]() Bumps [github.com/nats-io/nats-server/v2](https://github.com/nats-io/nats-server) from 2.11.3 to 2.11.7. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/nats-io/nats-server/releases">github.com/nats-io/nats-server/v2's releases</a>.</em></p> <blockquote> <h2>Release v2.11.7</h2> <h2>Changelog</h2> <p>Refer to the <a href="https://docs.nats.io/release-notes/whats_new/whats_new_211">2.11 Upgrade Guide</a> for backwards compatibility notes with 2.10.x.</p> <h3>Go Version</h3> <ul> <li>1.24.5 (<a href="https://redirect.github.com/nats-io/nats-server/issues/7047">#7047</a>)</li> </ul> <h3>Dependencies</h3> <ul> <li>golang.org/x/crypto v0.40.0 (<a href="https://redirect.github.com/nats-io/nats-server/issues/7061">#7061</a>)</li> <li>golang.org/x/sys v0.34.0 (<a href="https://redirect.github.com/nats-io/nats-server/issues/7061">#7061</a>)</li> </ul> <h3>Added</h3> <p>General</p> <ul> <li>The <code>SubjectMatchesFilter</code> function is now available as an exported function for embedded use (<a href="https://redirect.github.com/nats-io/nats-server/issues/7051">#7051</a>)</li> <li>The <code>leafz</code> monitoring endpoint now includes the connection ID (<a href="https://redirect.github.com/nats-io/nats-server/issues/7063">#7063</a>)</li> <li>The monitoring endpoint index page now includes the endpoint names on hover (<a href="https://redirect.github.com/nats-io/nats-server/issues/7066">#7066</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/7087">#7087</a>)</li> </ul> <h3>Improved</h3> <p>JetStream</p> <ul> <li>Consumers with inactivity thresholds should no longer age out before processing acks (<a href="https://redirect.github.com/nats-io/nats-server/issues/7107">#7107</a>)</li> <li>The Raft layer will no longer request store state on each apply (<a href="https://redirect.github.com/nats-io/nats-server/issues/7109">#7109</a>)</li> <li>Tombstones in Raft log compactions will now be written asynchronously, similar to purges (<a href="https://redirect.github.com/nats-io/nats-server/issues/7109">#7109</a>)</li> <li>When enabling per-message TTLs on a stream, existing messages with the <code>Nats-TTL</code> header are now scanned and processed (<a href="https://redirect.github.com/nats-io/nats-server/issues/7117">#7117</a>)</li> </ul> <h3>Fixed</h3> <p>General</p> <ul> <li>Message header lookups with common prefixes will now return correctly in all cases, fixing a problem where the headers could be sensitive to ordering (<a href="https://redirect.github.com/nats-io/nats-server/issues/7065">#7065</a>)</li> <li>Validate that the <code>default_sentinel</code> JWT is a bearer token for auth callout (7074)</li> <li>The <code>$SYS.REQ.USER.INFO</code> endpoint should now only be answered by the local server, fixing cases where the endpoint may sometimes return without full connection details (<a href="https://redirect.github.com/nats-io/nats-server/issues/7089">#7089</a>)</li> </ul> <p>JetStream</p> <ul> <li>The Raft layer will require recovery and snapshot handling at startup before campaigning for a leadership election, fixing a situation where a node could continue with an outdated stream (<a href="https://redirect.github.com/nats-io/nats-server/issues/7040">#7040</a>)</li> <li>The Raft log will no longer be compacted until after a snapshot is written, improving crash resilience (<a href="https://redirect.github.com/nats-io/nats-server/issues/7043">#7043</a>)</li> <li>A race condition when shutting down Raft nodes which could result in no snapshot being written has been fixed (<a href="https://redirect.github.com/nats-io/nats-server/issues/7045">#7045</a>)</li> <li>Consumer pull requests that use <code>no_wait</code> or <code>expires</code> behaviour has been fixed with replicated consumers (<a href="https://redirect.github.com/nats-io/nats-server/issues/7046">#7046</a>)</li> <li>Pull consumers with an inactive threshold will now consider pending acks when determining inactivity, preventing the consumer from being deleted while messages are being processed (<a href="https://redirect.github.com/nats-io/nats-server/issues/7052">#7052</a>)</li> <li>Push consumers will now correctly error when trying to configure priority groups (<a href="https://redirect.github.com/nats-io/nats-server/issues/7053">#7053</a>)</li> <li>Committed entry objects will now be correctly returned to the pool on error, reducing allocations (<a href="https://redirect.github.com/nats-io/nats-server/issues/7064">#7064</a>)</li> <li>The time hash wheel used for per-message TTLs now correctly detects and expires messages with TTLs over an hour, previously it could take double the expected time (<a href="https://redirect.github.com/nats-io/nats-server/issues/7070">#7070</a>)</li> <li>A potential panic when selecting message blocks during TTL recovery has been fixed (<a href="https://redirect.github.com/nats-io/nats-server/issues/7072">#7072</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
---|---|---|
.github | ||
appservice | ||
build | ||
clientapi | ||
cmd | ||
contrib | ||
docs | ||
federationapi | ||
helm | ||
internal | ||
mediaapi | ||
relayapi | ||
roomserver | ||
setup | ||
syncapi | ||
test | ||
userapi | ||
.dockerignore | ||
.gitignore | ||
.golangci.yml | ||
are-we-synapse-yet.list | ||
are-we-synapse-yet.py | ||
build-dendritejs.sh | ||
CHANGES.md | ||
CONTRIBUTING.md | ||
dendrite-sample.yaml | ||
Dockerfile | ||
go.mod | ||
go.sum | ||
LICENSE | ||
LICENSE-COMMERCIAL | ||
README.md | ||
run-sytest.sh | ||
show-expected-fail-tests.sh | ||
sytest-blacklist | ||
sytest-whitelist | ||
test-dendritejs.sh |
Dendrite
Dendrite is a second-generation Matrix homeserver written in Go. It intends to provide an efficient, reliable and scalable alternative to Synapse:
- Efficient: A small memory footprint with better baseline performance than an out-of-the-box Synapse.
- Reliable: Implements the Matrix specification as written, using the same test suite as Synapse as well as a brand new Go test suite.
- Scalable: can run on multiple machines and eventually scale to massive homeserver deployments.
Dendrite is beta software, which means:
- Dendrite is ready for early adopters. We recommend running Dendrite with a PostgreSQL database.
- Dendrite has periodic releases. We intend to release new versions as we fix bugs and land significant features.
- Dendrite supports database schema upgrades between releases. This means you should never lose your messages when upgrading Dendrite.
This does not mean:
- Dendrite is bug-free. It has not yet been battle-tested in the real world and so will be error prone initially.
- Dendrite is feature-complete. There may be client or federation APIs that are not implemented.
- Dendrite is ready for massive homeserver deployments. There is no high-availability/clustering support.
Currently, we expect Dendrite to function well for small (10s/100s of users) homeserver deployments as well as P2P Matrix nodes in-browser or on mobile devices.
If you have further questions, please take a look at our FAQ or join us in:
- #dendrite:matrix.org - General chat about the Dendrite project, for users and server admins alike
- #dendrite-dev:matrix.org - The place for developers, where all Dendrite development discussion happens
- #dendrite-alerts:matrix.org - Release notifications and important info, highly recommended for all Dendrite server admins
Requirements
See the Planning your Installation page for more information on requirements.
To build Dendrite, you will need Go 1.21 or later.
For a usable federating Dendrite deployment, you will also need:
- A domain name (or subdomain)
- A valid TLS certificate issued by a trusted authority for that domain
- SRV records or a well-known file pointing to your deployment
Also recommended are:
- A PostgreSQL database engine, which will perform better than SQLite with many users and/or larger rooms
- A reverse proxy server, such as nginx, configured like this sample
The Federation Tester can be used to verify your deployment.
Get started
If you wish to build a fully-federating Dendrite instance, see the Installation documentation. For running in Docker, see build/docker.
The following instructions are enough to get Dendrite started as a non-federating test deployment using self-signed certificates and SQLite databases:
$ git clone https://github.com/element-hq/dendrite
$ cd dendrite
$ go build -o bin/ ./cmd/...
# Generate a Matrix signing key for federation (required)
$ ./bin/generate-keys --private-key matrix_key.pem
# Generate a self-signed certificate (optional, but a valid TLS certificate is normally
# needed for Matrix federation/clients to work properly!)
$ ./bin/generate-keys --tls-cert server.crt --tls-key server.key
# Copy and modify the config file - you'll need to set a server name and paths to the keys
# at the very least, along with setting up the database connection strings.
$ cp dendrite-sample.yaml dendrite.yaml
# Build and run the server:
$ ./bin/dendrite --tls-cert server.crt --tls-key server.key --config dendrite.yaml
# Create an user account (add -admin for an admin user).
# Specify the localpart only, e.g. 'alice' for '@alice:domain.com'
$ ./bin/create-account --config dendrite.yaml --username alice
Then point your favourite Matrix client at http://localhost:8008
or https://localhost:8448
.
Progress
We use a script called "Are We Synapse Yet" which checks Sytest compliance rates. Sytest is a black-box homeserver test rig with around 900 tests. The script works out how many of these tests are passing on Dendrite and it updates with CI. As of January 2023, we have 100% server-server parity with Synapse, and the client-server parity is at 93% , though check CI for the latest numbers. In practice, this means you can communicate locally and via federation with Synapse servers such as matrix.org reasonably well, although there are still some missing features (like SSO and Third-party ID APIs).
We are prioritising features that will benefit single-user homeservers first (e.g Receipts, E2E) rather than features that massive deployments may be interested in (OpenID, Guests, Admin APIs, AS API). This means Dendrite supports amongst others:
- Core room functionality (creating rooms, invites, auth rules)
- Room versions 1 to 10 supported
- Backfilling locally and via federation
- Accounts, profiles and devices
- Published room lists
- Typing
- Media APIs
- Redaction
- Tagging
- Context
- E2E keys and device lists
- Receipts
- Push
- Guests
- User Directory
- Presence
- Fulltext search
Contributing
We would be grateful for any help on issues marked as Are We Synapse Yet. These issues all have related Sytests which need to pass in order for the issue to be closed. Once you've written your code, you can quickly run Sytest to ensure that the test names are now passing.
If you're new to the project, see our Contributing page to get up to speed, then look for Good First Issues. If you're familiar with the project, look for Help Wanted issues.
Copyright & License
Copyright 2017 OpenMarket Ltd Copyright 2017 Vector Creations Ltd Copyright 2017-2025 New Vector Ltd
This software is dual-licensed by New Vector Ltd (Element). It can be used either:
(1) for free under the terms of the GNU Affero General Public License (as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version); OR
(2) under the terms of a paid-for Element Commercial License agreement between you and Element (the terms of which may vary depending on what you and Element have agreed to). Unless required by applicable law or agreed to in writing, software distributed under the Licenses is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the Licenses for the specific language governing permissions and limitations under the Licenses.