-
Notifications
You must be signed in to change notification settings - Fork 147
Description
Environment
- Server version: 8.0.0-alpha.1
- Node.js version: v25.2.1
- npm version: 11.6.2
Description
This is not a bug but neither a future request. Pretty much suggestion to improve configs.
- https://github.com/search?q=repo%3ACommunitySolidServer%2FCommunitySolidServer%20urn%3Asolid-server%3Adefault%3ABackendKeyValueStorage&type=code
- https://github.com/search?q=repo%3ACommunitySolidServer%2FCommunitySolidServer%20urn%3Asolid-server%3Adefault%3ABackendKeyValueStorage&type=code
It looks like LockStorage and BackendKeyValueStorage are only used with memory locks.
Filesystem has a default location in a constructor https://github.com/CommunitySolidServer/CommunitySolidServer/blob/versions/next-major/src/util/locking/FileSystemResourceLocker.ts#L88
And Redis seems to use prefixes
https://github.com/CommunitySolidServer/CommunitySolidServer/blob/versions/next-major/src/util/locking/RedisLocker.ts#L16-L18
Until something else uses LockStorage it might be better to just create it directly in
config/util/resource-locker/memory.json
Currently configuring not in-memory urn:solid-server:default:KeyValueStorage with in-memory urn:solid-server:default:BackendKeyValueStorage (just for memory locks) requires bit extra configuration.
Based on a quick matrix chat, I understood that this one doesn't seem to make much sense any more
| "@id": "urn:solid-server:default:BackendKeyValueStorage", |