No "Register" button when WebID is disabled

Comienza reproduciendo la página principal del servidor con WebID desactivado y compárala con el flujo de registro inicial cuando WebID está activado; revisa config.json y la configuración de /public descrita en el informe. Se considera terminado si el registro y la creación de los directorios necesarios funcionan con WebID desactivado, o si se documentan el comportamiento plain-LDP compatible y la configuración.

This may fall into the category of "it's a feature, not a bug". But here goes...

We're using node-solid-server primarily as an LDP server for some research software we're developing, but are using the directory structure created for a single-user Solid deployment; specifically, the /public directory. Initially, I installed and tested with WebID enabled, performed the initial user registration, had software do the authentication dance, and all was fine.

But other software doesn't do authentication, so we tried setting up a new server with WebID disabled so we could use the basic LDP capabilities. Having done this, we found that there was no "Register" button on the server front page, and without registering a user, some of the directory structures (/public, etc.) appear not be be created.

Our workaround is to start with WebID enabled, perform the initial user registration, then edit the config.json file to disable webID, and this seems to work for us (so far).

This behaviour was slightly surprising for us, and it did take us a little while to figure out what was happening. If this is considered to be the desired behaviour, I'd suggest that a note in the documentation describing how to use the server as a plain LDP platform might be helpful.