Question: How can I most efficiently stream from many relays? about strfry

[hoytech]

As I said in another comment, I want to build a strfry router that would let you do this with a single plugin. I don't have a timeframe for this, but maybe I can get a basic solution to this problem as a start.

[hoytech]

I have pushed a commit that implements strfry router, and this will be in the next release. Docs are here: https://github.com/hoytech/strfry/blob/master/docs/router.md

I kind of think of this like "nginx for nostr". It lets you manage many up/down/both streams to remote relays using a single process and config file, and you can edit that config file without interrupting existing streams (mostly).

You can also use nostr filters and/or plugins to filter the traffic in both up and down directions, independently.

[IngwiePhoenix]

Just a thought: Templated SystemD units?

# [email protected]
[Unit]
Description=strfry relay: %i

[Service]
ExecStart=/usr/local/bin/strfry stream wss://%i --dir both

[Install]
WantedBy=multi-user.target

Should allow to systemctl start [email protected], as %s is...

the string between the first "@" character and the type suffix. Empty for non-instantiated units.

via: https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Specifiers

This could possibly be extended to depend on a root-service for the actual relay.

Thoughts?

[IngwiePhoenix]

I adapted the Headscale SystemD unit, so this could be a root unit.

[Unit]
After=syslog.target
After=network.target
Description=strfry (Nostr Relay)

[Service]
Type=simple
User=strfry
Group=strfry
ExecStart=/usr/local/bin/strfry relay
Restart=always
RestartSec=5

#If needed, this can be used to pass environment vars.
#Could be useful for passing data and other storage dirs?
#Environment="key=value"

WorkingDirectory=/var/lib/strfry
ReadWritePaths=/var/lib/strfry

AmbientCapabilities=CAP_NET_BIND_SERVICE CAP_CHOWN
CapabilityBoundingSet=CAP_NET_BIND_SERVICE CAP_CHOWN
LockPersonality=true
NoNewPrivileges=true
PrivateDevices=true
PrivateMounts=true
PrivateTmp=true
ProcSubset=pid
ProtectClock=true
ProtectControlGroups=true
ProtectHome=true
ProtectHome=yes
ProtectHostname=true
ProtectKernelLogs=true
ProtectKernelModules=true
ProtectKernelTunables=true
ProtectProc=invisible
ProtectSystem=strict
RemoveIPC=true
RestrictAddressFamilies=AF_INET AF_INET6
RestrictNamespaces=true
RestrictRealtime=true
RestrictSUIDSGID=true
SystemCallArchitectures=native
SystemCallFilter=@chown
SystemCallFilter=@system-service
SystemCallFilter=~@privileged
UMask=0077

[Install]
WantedBy=multi-user.target

This can be adapted to be a template, as described before, just with an added Requires=strfry.service in the [Service] section (as explained here).

Hope this helps :)

[Giszmo]

@IngwiePhoenix thanks for your effort. It certainly helps to learn about using SystemD but I think it doesn't address well the "many relays" part.