You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Update all home resources, append a trailing slash
Update all the values that point to home resources
Rebuild indexes.
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
The text was updated successfully, but these errors were encountered:
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
home
instead 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 toThe text was updated successfully, but these errors were encountered: