Nixos deployment

I don't think we've previously had any Nix/NixOS/nixpkgs related entries in TWIM, so I'll start ^^

We now have a module for Heisenbridge and Conduit, which makes it super easy to deploy any of those services: My configuration for Heisenbridge is 21 lines long, and Conduit is only 11 lines. You can browse the available configuration options online: services.matrix-conduit, services.heisenbridge (note that some of them are freeform and simply forward to the upstream configuration).

For support, join our Matrix space at #nix:nixos.org and the Matrix-Nix channel: #matrix-nix:transformierende-gesellschaft.org

Nixos deployment

I don't think we've previously had any Nix/NixOS/nixpkgs related entries in TWIM, so I'll start ^^

We now have a module for Heisenbridge and Conduit, which makes it super easy to deploy any of those services: My configuration for Heisenbridge is 21 lines long, and Conduit is only 11 lines. You can browse the available configuration options online: services.matrix-conduit, services.heisenbridge (note that some of them are freeform and simply forward to the upstream configuration).

For those that are not into NixOS, a module is the code that turns the declarative configuration files into your running system setup. As an example, if you enable services.heisenbridge the following things are done for you:

• Create a new heisenbridge user and group for the service
• Create and manage the registration file for the homeserver (i.e. automatically regenerate it after the configuration changed)
• Create a systemd service that runs the heisenbridge command with the requested bridge configuration. The unit also sets a few systemd security hardening options.

For support, join our Matrix space at #nix:nixos.org and the Matrix-Nix channel: #matrix-nix:transformierende-gesellschaft.org

In reply to @piegames:matrix.org
Feedback?

In reply to @piegames:matrix.org
Janne Heß: the modules are on unstable only

In reply to @janne.hess:helsinki-systems.de
Also I'd go for We now have a module for Heisenbridge and Conduit → The latest release 21.11 of the [NixOS](https://nixos.org) distribution has extended Matrix support to also include [Conduit](https://blah) and [Heisenbridge](https://blah) packages and modules (Synapse and Element have already been supported in previous releases). (maybe?)

Nixos deployment

I don't think we've previously had any Nix/NixOS/nixpkgs related entries in TWIM, so I'll start ^^

The current unstable channel has extended its Matrix ecosystem support to also include Heisenbridge and Conduit packages and modules. This makes it super easy to deploy any of those services: For example, my configuration for Heisenbridge is 21 lines long, and Conduit is only 11 lines. You can browse the available configuration options online: services.matrix-conduit, services.heisenbridge (note that some of them are freeform and simply forward to the upstream configuration).

For those that are not into NixOS, a module is the code that turns the declarative configuration files into your running system setup. As an example, if you enable services.heisenbridge the following things are done for you:

• Create a new heisenbridge user and group for the service
• Create and manage the registration file for the homeserver (i.e. automatically regenerate it after the configuration changed)
• Create a systemd service that runs the heisenbridge command with the requested bridge configuration. The unit also sets a few systemd security hardening options.

For support, join our Matrix space at #community:nixos.org and its Matrix-Nix channel: #matrix-nix:transformierende-gesellschaft.org