Create a configuration with separate CSS instances for different responsibilities

[RubenVerborgh]

The CSS bundles several components such as a storage server, an identity provider, a WebID minter, an account manager, etc.
Can we create a configuration in which different CSS instances play these roles?

[MisterTimn]

Interesting, are there examples of how CSS has to be setup to facilitate this? And is this behavior then also enforced by the CSS?

A configuration like this is possible but might also warrant a separate chart. We can re-use the CSS base chart as a dependency with aliases in a parent chart for that configuration.

[RubenVerborgh]

I'll defer to @tomhgmns and @wouteraj, who suggested this idea.

[tomhgmns]

Sorry, I only noticed you've mentioned me today!

Basically, the idea has both a philosophical and practical motivation.

Philosophically, Solid is designed to standardise interaction between storage, login methods, personal identifiers authorisation agents, authorisation servers and applications. The fact that the Community Solid Server bundles many of those component in one package very misleading with respect the purpose of the Solid standard. People that are exploring Solid by playing around with the CSS might not learn the most essential parts of Solid.

Practically, in our WebID service (i.e. use.id), we rely solely on the storage component of the CSS. We do not rely on the account management, IDP, etc.