Conversation
The port has no meaning in this context and will allow compatibility with Windows where colon are forbidden in file/folder names. It has not impact on `solidcommunity.net` nor `inrupt.net`, or any of podProvider that do not use a specific port. see issue SolidOS/solid-panes#262
|
This does mean that server admins should now be cautioned that IF they run multiple Solid server instances on a single host, they will need to set each Solid server to use a different filesystem directory as their root to avoid possible folder-tree collisions. (This is probably a SHOULD anyway, but with this change it becomes a MUST.) |
|
This already is the case when using NSS, Pod folder is the hostname and do not include the port. I have not seen anything in specification relative to filesystem. The above case do not relate to the same thing. It is the name of a folder inside a pod folder. It could be named If a unique name was wanted it could be a webId |
|
OK, I misinterpreted your comment about "any of podProvider that do not use a specific port" to mean that this would impact any podProvider that did use a specific port. |
|
Individual pod directories are currently named without a port. My account directory on https://solid.hll.nu:7443 is named rogerfgay.solid.hll.nu |
|
Perhaps we can just remove the ':' to avoid collisions. |
3 participants
The port has no meaning in this context and will allow compatibility with Windows where colon are forbidden in file/folder names.
It has not impact on
solidcommunity.netnorinrupt.net, or any of podProvider that do not use a specific port.see issue SolidOS/solid-panes#262