Skip to content

After NSS2CSS migration : Root no longer has a Link header with rel="type" to space:storage #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
bourgeoa opened this issue Mar 17, 2025 · 1 comment

Comments

@bourgeoa
Copy link

@joachimvh
After migration of https://solidcommunity.net from NSS2CSS Root no longer has a Link header with rel="type" to space:storage.
see solid/solidcommunity.net#78

When creating a new account the new pod shows a Root with a Link header with rel="type" to space:storage.

The issue should come from the migration.

  1. I checked the profile and don't see any notable difference.

  2. The migration was done with :

  • creating a new server and let it running while migrating
  • file creating the user accounts in www/.internal/accounts/data and www/.internal/accounts/index
  • pods where copied from NSS

The only difference I can see is in the root/.meta

  • in first place does is it checked from the profile ?
  • where does CSS takes the space:Storage Header from ?
  • What solution can be implemented ?
    • if I delete the root/.meta will it be recreated ?
    • else can we simply add a triple : <> a <http://www.w3.org/ns/pim/space#Storage> in root/.meta
@joachimvh
Copy link
Member

  • else can we simply add a triple : <> a <http://www.w3.org/ns/pim/space#Storage> in root/.meta

This should fix the issue yes. A resource with that triple in its metadata will receive the corresponding link header. New pods will have this as it is part of the template: https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.1.6/templates/pod/base/.meta

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants