modules: [modules] config + example service crate + SDK guide
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:
parent
596630df53
commit
e0bb3a1fea
9 changed files with 254 additions and 7 deletions
8
Cargo.lock
generated
8
Cargo.lock
generated
|
|
@ -286,6 +286,7 @@ dependencies = [
|
|||
"base64",
|
||||
"fedserv-api",
|
||||
"fedserv-chanserv",
|
||||
"fedserv-example",
|
||||
"fedserv-inspircd",
|
||||
"fedserv-nickserv",
|
||||
"hmac",
|
||||
|
|
@ -317,6 +318,13 @@ dependencies = [
|
|||
"fedserv-api",
|
||||
]
|
||||
|
||||
[[package]]
|
||||
name = "fedserv-example"
|
||||
version = "0.0.1"
|
||||
dependencies = [
|
||||
"fedserv-api",
|
||||
]
|
||||
|
||||
[[package]]
|
||||
name = "fedserv-inspircd"
|
||||
version = "0.0.1"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue