-
Notifications
You must be signed in to change notification settings - Fork 3
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
KBI0028: Notes on Sciebo/Nextcloud share URLs #104
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for writing this up. Great technical details that are sensible and can be followed easily.
I made some suggestions that are mostly about improving the structure and readability of the document as a whole.
This KBI made me think that something like a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a great addition!
super insightful! Thanks for writing this up! |
Co-authored-by: Stephan Heunis <s.heunis@fz-juelich.de>
Thanks for the reviews! @jsheunis I applied most of your suggestions, but then pushed further tweaks, sometimes refining the suggestions further. I rejected the suggestion in introduction, but pushed a change that's similar in spirit while remaining a short paragraph (note that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Happy with the edited/committed changes 👍 👍
Discovered that by accident today - registered URL would be urlquoted anyway, plus uncurl tries to split the match pattern into match patterns.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great to have! Thanks @mslw!
Thanks again for the reviews, merging! |
It did not come up as a support event (i.e. "nobody asked for this"), but this goes back to something we considered for an archival request (internal issue tracker) and something I later explored for myself, so I think knowledge base is an useful place to document that with better visibility.
Features Nextcloud / Sciebo specific details, and a practical example of an uncurl remote. Writing it up was very educational for me.