!vxTmkuJzhGPsMdkAOc:transformierende-gesellschaft.org

NixOS Matrix Subsystem

158 Members
Coordination and discussion about the matrix subsystem in NixOS - https://wiki.nixos.org/wiki/Matrix81 Servers

Load older messages


SenderMessageTime
16 Sep 2023
@hexa:lossy.networkhexaTIL: https://github.com/matrix-org/synapse/blob/develop/flake.nix17:18:04
@hexa:lossy.networkhexacreated by anoadragon45317:18:38
@sumner:nevarro.spaceSumner EvansYeah. It's kinda a weird setup for dev tbh. But if you modify a couple things it's usable.17:31:45
18 Sep 2023
@hexa:lossy.networkhexaworker support 👏17:54:49
@hexa:lossy.networkhexathanks everyone17:55:09
@hexa:lossy.networkhexanow, who will manage that nasty nginx vhost for me? 🤡17:55:35
@ma27:nicht-so.sexyma27I'm sure there are at least three people with config for that :>17:59:07
@dandellion:dodsorf.asDandellion

I think Ma27 seemed quite negative about this generally, But personally I think just putting the maps inside services.nginx.commonHttpConfig is more than adequate even without RFC-42 nginx (Which I think is basically impossible without introducing some kind of DAG system similar to home-manager)

But I'll be changing my module to match the nixpkgs implementation and work towards upstreaming the autoconfig stuff

18:01:57
@hexa:lossy.networkhexaI think it is much more straightforward than nextcloud 😄 18:02:44
@hexa:lossy.networkhexaand maintaining the map in nixpkgs would require a fair amount of testing and attention when updating the package18:03:22
@dandellion:dodsorf.asDandellionworst case it just falls back to the main process18:03:51
@dandellion:dodsorf.asDandellionit'd be additive in any case really18:04:04
@hexa:lossy.networkhexa Oh yeah, that should work for most cases, except for enable_media_repo = false or send_federation = false 18:04:43
@hexa:lossy.networkhexaalso stream writers are a bit more complex with the different types they can be configured to handle18:05:58
@dandellion:dodsorf.asDandellionstream writers are problematic yep18:06:17
@dandellion:dodsorf.asDandellionor, at least, slightly annoying18:06:31
@hexa:lossy.networkhexaevents can be striped across multiple workers, most other things (typing, to_device, account_data, receipts, presence) cannot18:07:06
@hexa:lossy.networkhexasynapse will fail to boot when you configure a list where it expects a string, ask me how I know18:07:55
@hexa:lossy.networkhexa * synapse will fail to boot when you configure a list of workers where it expects a just a single one, ask me how I know18:08:13
@dandellion:dodsorf.asDandellionthat's right, it's also why my module only supports event persisters for now18:09:00
@ma27:nicht-so.sexyma27
In reply to @hexa:lossy.network
synapse will fail to boot when you configure a list of workers where it expects a just a single one, ask me how I know
oh, you too :D
18:09:04
@ma27:nicht-so.sexyma27currently on the phone, will respond later18:09:16
@dandellion:dodsorf.asDandellionsince abstracting the other stream writers required a little more work at the time18:09:33
@dandellion:dodsorf.asDandellion * since abstracting the other stream writers properly required a little more work at the time18:09:45
@hexa:lossy.networkhexaas the worker setup is very brittle, we should probably try to co-maintain most of the thing18:12:06
@hexa:lossy.networkhexa * as the worker setup is very brittle, we should probably try to co-maintain most of the code18:12:12
@hexa:lossy.networkhexa * as the worker setup is very brittle, we should probably try to co-maintain most of the code required for a productive worker setup18:12:43
@hexa:lossy.networkhexaand not let everyone come up with a weird downstream solution18:12:50
@hexa:lossy.networkhexa * and not let everyone come up with an even weirder downstream solution18:13:07
@f0x:pixie.townf0x
In reply to @hexa:lossy.network
and not let everyone come up with an even weirder downstream solution
ha ha sweats
18:14:42

Show newer messages


Back to Room ListRoom Version: 4