Filesystem socket
Every route the guest filesystem socket answers, and every shape it answers with.
What the host serves on the unix socket [filesystem] socket names in config.toml. It is off
unless that section is there. File listings is the guide; this is
every route and every shape, rendered from crates/nibrunnerd/filesystem.openapi.json.
The socket answers reads and takes no input. Listing an app that is asleep wakes it, the way a request reaching it would.
GET
/apps/{appId}/filesPath Parameters
appId*string
The app to ask, as desired.json names it.
Match
^[A-Za-z0-9][A-Za-z0-9_-]{0,62}$Query Parameters
path*string
The directory to list, percent-encoded.
Match
^/$|^(/(?!\.\.?(/|$))[^/\\"'\x00-\x1f]+)+$Length
length <= 4096Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl --unix-socket /run/nibrunner/filesystem.sock \ 'http://localhost/apps/app-7/files?path=%2Fdata'{ "entries": [ { "kind": "file", "modifiedAt": "string", "name": "string", "sizeBytes": 0 } ], "path": "string", "truncated": true}