flotilla/e2e/harness/zooid/docker/config/other.toml
2026-08-07 13:11:12 -07:00

44 lines
1.6 KiB
TOML

# A second virtual relay, identical in policy to space.toml, for specs that need two spaces on
# different relays — outbox routing, cross-space isolation. zooid is multi-tenant, so this costs a
# file and no extra process.
#
# `host` must equal the Host header the harness sends, which is the hostname of the url the client
# is given; anything else gets a 404 from the dispatcher instead of a relay. Keep it in step with
# `tenants` in harness/zooid/config.ts, and see harness/zooid/transport.ts for why it is a name
# that resolves nowhere.
host = "other.test"
schema = "e2e_other"
secret = "07be7000000000000000000000000000000000000000000000000000000000e7"
[info]
# Served to the client as nip-11. `name` is what a spec sees as the space's name, so it matches the
# name scenarios pass to `relay()`. `pubkey` is the owner, and here it is the relay's own key (the
# pubkey for `secret`) so that [roles.admin] below is the only thing granting a test identity
# can_manage.
name = "other"
pubkey = "d9220af5f36469d17322f41902b6b30dad1869cbb473b35f5e8f8d8e924f36b8"
description = "Throwaway relay for Flotilla's end-to-end suite."
[policy]
public_read = false
public_write = false
public_join = true
strip_signatures = false
[groups]
enabled = true
[management]
enabled = true
# Blossom and push are off, and [livekit] is omitted entirely, because each of them would have
# the relay or the client talk to a service the test did not create.
[blossom]
enabled = false
[push]
enabled = false
[roles.admin]
pubkeys = ["6ada7b6eabb3a8349f88667d278a275c704b553a7c57f9d8156555986884a08e"]
can_manage = true