pasterwelove.blogg.se - Whm list directory contents permission

#Whm list directory contents permission update

I like the security of SVN+SSH over just SVN.

Trying to maintain master user/group permissions of file and folders to the original user account, and not the account of the updatee.

multiple user accounts specified given the structure of WHM.

Now this was long winded enough to give an overview of exactly what I'm trying to accomplish, just incase I'm going about this arse-over-tit and there's a far easier solution. As Bob belongs to Dev I can set the permissions correctly with CHMOd, but It appears CHGRP is throwing back operation errors. How can I get it so that with the set of user permissions Bob has available, to change the owner and group owner of that file to reflect "site1" "site1". When I wish to add a file or folder to /home/site1, say Bobs_file, it then looks like this drwxrwxr-x.

#Whm list directory contents permission update

So I then added site1 to Joe and Bobs secondary groups so that the SVN update will correctly allow access to these files. So site1 is sthe owner and group owner of those files and folders. Which looks a little something like this drwxrwxr-x. I then changed this to try and factor in group permission updates, instead of straight 777.Įach folder in /home/site1/public_html intially gets given a chmod of 664, and each folder 775 Post commit triggers, updates the site, and then sets 777 on each file within the webfront. I have the master /svn folders set up for both read and write access to this group, and it works great. Joe and Bob both belong to a group called "Dev". Through my testing of this setup, I've only managed to get it working by giving what is being updated permissions of 777, so that Joe and Bob can both read and write access to webfront directories for each of the sites. Here's the cavet, and ultimately my problem.

So I've done the easy bit, managed to get SVN working with these "maintainers" so that when an SVN commit occurs, the changes are checked out and go live perfectly. Joe and Bob both have commandline access to the server through thier respective limited accounts. There are two regular maintainers of these sites, we'll call them Joe and Bob. svn blocked through the apache configuration). Not if it was a single email account which I had access too there are likely much simpler options using webmail or an email client to get the same outcome. Now, updating these sites is accomplished using SVN, and through the use of a post commit script to auto update these sites (With. WHM: List Largest Emails In An Account With Subject I recently needed to find the largest emails in various email accounts and share the size and subject.

Now, with the WHM setup, each site has a user/group defined for them, we'll keep these users/groups called site1,site2 for simplicity reasons. Imagine a production server running WHM with various sites. I'll try my best to explain how I'm trying to set up this system.