Open lnnrtwttkhn opened 1 year ago
huh, it also looks like there's something weird happening to the credential, as well. Which datalad-next
version is this?
yes, sorry, forgot about the version details:
All on macOS 12.6.3 (Monterey) with M1.
Thanks! I'm trying to reproduce this, and set up an account. Initially, I got an "insufficient storage" error because it seems that I need to configure an external storage location for each folder.
What kind of storage do you have configured?
I followed @mih's (great!) video instructions:
https://owncloud.gwdg.de/remote.php/nonshib-webdav/
- usually at the bottom left of the web interface)<dataset_name>
to webdav address):datalad create-sibling-webdav \
--dataset . \
--name owncloud-gwdg \
--mode filetree \
'https://owncloud.gwdg.de/remote.php/nonshib-webdav/<dataset-name>'
datalad push --to owncloud-gwdg
That's all. So I didn't configure any storage location manually via the web interface.
huh, interesting! Thanks, I'll try get some storage space, I have none :D
Hey, 2 cents from my side:
datalad credentials
. The default name template is something like webdav-username-address
.git annex export HEAD --to owncloud-gwdg-storage --json --json-error-messages
to see what exactly git-annex does. But since everything worked in the end, there is no need.I had similar issues with another hosting provider #202 - but there it was a spurious but persistent 404 error for a DELETE request. So I waved it of with "weird server behaviour". Not even sure if related, just linking so that we can keep track of.
From reading the issue I have no idea what may have caused the intermittent 403 error, but probably the credentials are worth looking into.
Hey all, I tried
create_sibling_webdav
for the first time together with GWDG's ownCloud.I used the MoAEpilot dataset as an example, as described in the "Walk-through: Amazon S3 as a special remote" chapter in the DataLad Handbook.
When pushing the dataset to ownCloud for the first time, errors occurred related to
.datalad/config
andsub-01/func/sub-01_task-auditory_events.tsv
(see below).The file were transferred on a second push though.
So not a huge issue but just reporting this in case you see any opportunity to improve something on the DataLad side of things.
Thanks and keep up the good work!
Documentation
Configuring the WebDAV sibling
Output:
Pushing to WebDAV sibling:
Output