add templates parameter

[bourgeoa]

Feature description

To create pods with a different templates than the default one.
This is basically the case when using mashlib.

Actually the only way to import a templates-folder is by making a cp -r templates-folder/ node_modules/@solid/communitys-server/
This works but is not very friendly and need to be redone each time node_modules are updated or rebuild with npm ci

Adding a parameter would make it much easier.

[joachimvh]

You can use a small Components.js configuration for this using Components.js new override feature.

Specifically, the pod template folder is defined here:

CommunitySolidServer/config/identity/pod/resource-generators/templated.json

Lines 5 to 8 in bf0e35b

	"comment": "Generates resources based on the templates stored in the template folder.",
	"@id": "urn:solid-server:default:ResourcesGenerator",
	"@type": "TemplatedResourcesGenerator",
	"templateFolder": "@css:templates/pod",

You could create a new Components.js config that overrides that template folder like so:

{
  "@context": "https://linkedsoftwaredependencies.org/bundles/npm/@solid/community-server/^5.0.0/components/context.jsonld",
  "@graph": [
    {
      "@type": "Override",
      "overrideInstance": { "@id": "urn:solid-server:default:ResourcesGenerator" },
      "overrideParameters": {
        "@type": "TemplatedResourcesGenerator",
        "templateFolder": "/my/template/folder"
      }
    }
  ]
}

You could then start the server with npm start -- -c config/file.json my-override-config.json to change it to the new template folder value (or combine that config with yours if you already have a custom one). This will survive rebuilds/reinstalls (but might break on a new major release).

[bourgeoa]

Thanks I shall try it.

[bourgeoa]

Works perfectly.
I discovered with your example that you can have multiple config-file

[joachimvh]

Works perfectly. I discovered with your example that you can have multiple config-file

Yes, this is a new feature that was just added in v5.1.0.

Note that this solution can break on a new major version release as config structure might change meaning the solution will have to adapt then.