fedserv/echo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

modules: [modules] config + example service crate + SDK guide

Browse source 
A [modules] block selects which services start (default: NickServ + ChanServ);
main.rs constructs each compiled-in module only when named, so a node can run a
subset and optional modules ship dormant. Add fedserv-example, a minimal
read-only Service that depends on fedserv-api alone -- the template a new
pseudo-client is copied from, enabled by adding "example" to the config.
MODULES.md documents writing and registering a service or protocol module.
This commit is contained in:
Jean Chevronnet 2026-07-13 01:48:09 +00:00
parent 596630df53
commit e0bb3a1fea
No known key found for this signature in database
9 changed files with 254 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

5
config.example.toml
View file

@ -35,3 +35,8 @@ protocol = 1206 # InspIRCd link protocol version (1206 = insp4, 1205
# [grpc.tls] # omit for plaintext (fine on a private/loopback hop)
# cert = "certs/node.crt"
# key = "certs/node.key"
# Which service modules to start. Omit this section for the built-in NickServ +
# ChanServ. Add "example" to also start the example template service.
# [modules]
# services = ["nickserv", "chanserv"]