The CSS configuration used by all CSS containers in docker-compose*.yml
is controlled by /common/css.json.
See also the documentation on how to configure your CSS server.
The template is based on the example configuration generated by the configuration generator:
| configurator versioned URL | settings |
|---|---|
| https://communitysolidserver.github.io/configuration-generator/v7/ | CSS-config-generator-input-for-v7 |
The following section was added to the "@graph" array by hand:
{
"comment": "The location of the new pod templates folder.",
"@type": "Override",
"overrideInstance": {
"@id": "urn:solid-server:default:PodResourcesGenerator"
},
"overrideParameters": {
"@type": "StaticFolderGenerator",
"templateFolder": "/config/pod-template"
}
},
{
"comment": "Where the WebID is located in the generated pod, relative to the root.",
"@type": "Override",
"overrideInstance": {
"@id": "urn:solid-server:default:PodCreator"
},
"overrideParameters": {
"@type": "BasePodCreator",
"relativeWebIdPath": "profile/card#me"
}
},The credentials (email, password) for the root pod were set to something non-default in this section:
{
"comment": [
"The login settings of the account of the root pod. ",
"It is advised to immediately change this password after starting the server."
],
"@type": "Override",
"overrideInstance": {
"@id": "urn:solid-server:default:RootPodInitializer"
},
"overrideParameters": {
"@type": "AccountInitializer",
"email": "...",
"password": "..."
}
}Note that the root pod is not used, but enabling a root pod currently is the only possible configuration-time solution to avoid public write and append access to the parent container of the other pod root containers:
the configuration setting Initialize root: Inaccessible root is not allowed if the configuration setting Solid protocol: Enabled is needed (which is the case).