In #505, we finally start parsing requested URLs as URLs instead of Strings. This will give all "home" URLs a trailing slash. E.g. https://atomicdata.dev ==> https://atomicdata.dev/.
This means that existing URLs to the main drives may not longer work.
In order to prevent users from getting issues, we should update their subjects when they switch to this newer system. I think that means we should add a function to migration.rs.
[x] Update all home resources, append a trailing slash
[x] Update all the values that point to home resources
[x] Rebuild indexes.
[x] Find a way to deal with Commits. => Ignore them, they become irrelevant
Commits
If the user has made commits to home instead of home/, then the commits no longer contain the correct Subject. Their contents need to be rewritten, which means the signatures no longer match the contents. So if someone would play back the commits, they would throw errors. A different approach is to
joepio
commented
2 months ago
In #505, we finally start parsing requested URLs as URLs instead of Strings. This will give all "home" URLs a trailing slash. E.g.
https://atomicdata.dev==>https://atomicdata.dev/.This means that existing URLs to the main drives may not longer work.
In order to prevent users from getting issues, we should update their subjects when they switch to this newer system. I think that means we should add a function to
migration.rs.Commits
If the user has made commits to
homeinstead ofhome/, then the commits no longer contain the correct Subject. Their contents need to be rewritten, which means the signatures no longer match the contents. So if someone would play back the commits, they would throw errors. A different approach is to