Hi, There is no way to automate this unfortunately.
The skeleton files are copied over and I don't think PHP's copy operation will preserve the permissions. I don't see any way of doing it that doesn't involve changing the PHP code or writing a small app. A cronjob ? (ugly but might work) Cheers, Vincent On 12/11/2014 01:51 PM, mourik jan heupink wrote: > Hi, > > I found /core/skeleton, but is there a way to adjust default permissions > for the ./files directory? > > MJ > > On 12/10/2014 05:31 PM, PB.Owncloud wrote: >> Just don't let www-data write to data/userX/files >> >> -- >> >> Pablo Berdaguer >> >> 10 de diciembre del 2014 16:18, "heupink" <[email protected]> escribió: >>> Hi Vincent, >>> >>> Ok, you misunderstood me. Suppose we have: >>> /mount1 >>> /mount2 >>> /mount3 >>> /mount4 >>> Like this, all data is not actually on the server running owncloud, but >>> on the samba servers where mount1-mount4 reside. >>> >>> What I would like to prevent is users creating a new >>> /directory5 >>> /file6.txt >>> >>> These files would end up on the server running owncloud. And I would >>> like to prevent THAT from happening. I want to force them to save >>> *EVERYTHING* under mount1/mount2/mount3/mount4. >>> >>> Therefore something like a switch to allow/disallow new 'toplevel' >>> folders/files to be created by users (/directory6 or /file6.txt) >>> >>> Of course under /mount1 they have whatever permissions they have there. >>> (depending on the username, group membership, etc, ect) (anyway: like >>> you say: that's not owncloud's concern) >>> >>> Is this clearer..? >>> >>> MJ >>> >>> On 12/10/2014 15:53, Vincent Petry wrote: >>> >>>> Hi, >>>> >>>> 1) Please raise a ticket using the issue template: >>>> https://raw.github.com/owncloud/core/master/issue_template.md >>>> >>>> 2) If I understand well, the situation is as follows, from the point of >>>> view of a user "user1": >>>> >>>> Have several external storage mount points: >>>> "/mount1" >>>> "/mount2" >>>> "/mount3" >>>> "/mount4" >>>> >>>> Use is not allowed to create/edit files/folders directly under >>>> "/mount1" >>>> but allowed to create/edit file/folders under "/mount1/subdir". >>>> >>>> I don't think it's ownCloud's responsibility to enforce such >>>> permissions, especially that these folders are on an external storage >>>> which itself has its own permissions. >>>> >>>> What you could do is: if "/mount1" is a SMB storage authenticated with >>>> the credentials from "user1", you could change the SMB storage's >>>> permissions to deny "user1" to change the content inside the root of >>>> it, >>>> outside of ownCloud. >>>> >>>> If the SMB mount is a Linux home "/home/user1" mounted as "/mount1" in >>>> OC, you could "chmod a-w /home/user1" but keep the write permissions on >>>> "/home/user1/subdir". >>>> >>>> Cheers, >>>> >>>> Vincent >>>> >>>> On 12/10/2014 03:47 PM, heupink wrote: >>>>> Hi Vincent, >>>>> >>>>>> 1) Probably a bug. Where are you renaming the folders ? In the admin >>>>>> page ? >>>>> >>>>> Yep, logged in as oc-admin, under admin. >>>>> >>>>>> 2) Not supported yet. See >>>>>> https://github.com/owncloud/core/issues/10198 >>>>> >>>>> The issue above seems to be: mounting one single external storage >>>>> provider as a 'base' for owncloud storage. >>>>> >>>>> What I'm asking is not about the 'base' (/) storage location, but >>>>> about predefined external locations, each with their own 'foldername' >>>>> in owncloud. (this is of course already possible) But: >>>>> >>>>> I would like to have a setting to allow or disallow new toplevel >>>>> folders and files to be created by our users. >>>>> >>>>> This is not what issue 10198 is about, or do I misunderstand issue >>>>> 10198? >>>>> >>>>> Thanks for the quick follow-up! >>>>> >>>>>> Cheers, >>>>>> >>>>>> Vincent >>>>>> >>>>>> On 12/10/2014 03:28 PM, heupink wrote: >>>>>>> Hi, >>>>>>> >>>>>>> We just upgraded to 7.0.4, upgrade went very smoothly, thanks! >>>>>>> >>>>>>> Two things: >>>>>>> >>>>>>> 1) When editing external storage, changing the 'folder name' does >>>>>>> not >>>>>>> always save. We have four different external storage, all using >>>>>>> SMB / >>>>>>> CIFS using OC login. (lovely new feature, btw!) >>>>>>> >>>>>>> Changing all four foldernames in a row caused only the first >>>>>>> change to >>>>>>> be saved. The others kept their old name. >>>>>>> Did anyone else notice this? Yes yes, then I guess it's a bug, and I >>>>>>> should submit a bugreport... >>>>>>> >>>>>>> 2) Is it possible to restrict file storage on owncloud to these four >>>>>>> predefined top-level folders? As in: prevent users to create >>>>>>> their own >>>>>>> folders/files structure, but make them use our four network shares. >>>>>>> >>>>>>> Kind regards, >>>>>>> MJ >>>>>>> _______________________________________________ >>>>>>> User mailing list >>>>>>> [email protected] >>>>>>> http://mailman.owncloud.org/mailman/listinfo/user >>>>>> >>>>>> _______________________________________________ >>>>>> User mailing list >>>>>> [email protected] >>>>>> http://mailman.owncloud.org/mailman/listinfo/user >>>>> >>>>> _______________________________________________ >>>>> User mailing list >>>>> [email protected] >>>>> http://mailman.owncloud.org/mailman/listinfo/user >>>> >>>> _______________________________________________ >>>> User mailing list >>>> [email protected] >>>> http://mailman.owncloud.org/mailman/listinfo/user >>> >>> _______________________________________________ >>> User mailing list >>> [email protected] >>> http://mailman.owncloud.org/mailman/listinfo/user >> _______________________________________________ >> User mailing list >> [email protected] >> http://mailman.owncloud.org/mailman/listinfo/user >> > _______________________________________________ > User mailing list > [email protected] > http://mailman.owncloud.org/mailman/listinfo/user
signature.asc
Description: OpenPGP digital signature
_______________________________________________ User mailing list [email protected] http://mailman.owncloud.org/mailman/listinfo/user
