(no commit message)
authornobodyinperson <nobodyinperson@web>
Tue, 13 Dec 2022 16:16:49 +0000 (16:16 +0000)
committeradmin <admin@branchable.com>
Tue, 13 Dec 2022 16:16:49 +0000 (16:16 +0000)
doc/forum/Handling_permissions_in_a_shared_folder.mdwn [new file with mode: 0644]

diff --git a/doc/forum/Handling_permissions_in_a_shared_folder.mdwn b/doc/forum/Handling_permissions_in_a_shared_folder.mdwn
new file mode 100644 (file)
index 0000000..7c26a63
--- /dev/null
@@ -0,0 +1,17 @@
+Hi everyone,
+
+Just wanted to ask how to handle the following situation:
+
+- shared computer, everyone has an unprivileged, non-sudoer account and logs in via ssh for example or JupyterHub (unprivileged terminal, no `sudo` possible from there).
+- shared directory (everyone in same group, all files owned by group, sticky bit, file owner varies)
+- git-annex repository on this shared directory
+
+Problem: git-annex operations fail depending on who the owner of the files is. As git-annex needs to `chmod` files (which is only possible as owner of the file), this is a problem. 
+
+A partial solution I've employed right now is to sudo-allow one specific command that recursively sets themselves as owner for the shared directory (including the git-annex repo). This however only works when `sudo` is working, which is not the case from JupyterHub...
+
+Any other ideas? (Except ditching the shared folder...)
+
+Cheers,
+
+Yann