Databases
StackOverflow2013
Postsdbo
POAvoid having subversion modify Linux file permissions.
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAvoid having subversion modify Linux file permissions.
    primarykey
    data
    text
    <p>All of my code base is being stored in a subversion repository that I disperse amongst my load balanced Apache web servers, making it easy to check out code, run updates, and seamlessly get my code in development onto production.</p> <p>One of the inconveniences that I'm sure there is a easy work around for (other than executing a script upon every checkout), is getting the Linux permissions set (back) on files that are updated or checked out with subversion. Our security team has it set that the <code>Owner</code> and <code>Group</code> set in the <em>httpd.conf</em> files, and all directories within the <code>documentRoot</code> receive permissions of 700, all non-executable files (e.g. *.php, *.smarty, *.png) receive Linux permissions of 600, all executable files receive 700 (e.g. *.sh, *.pl, *.py). All files must have owner and group set to <code>apache:apache</code> in order to be read by the httpd service since only the file owner is set to have access via the permissions.</p> <p>Every time I run an <code>svn update</code>, or <code>svn co</code>, even though the files may not be created (i.e. <code>svn update</code>), I'm finding that the ownership of the files is getting set to the account that is running the svn commands, and often times, the file permissions are getting set to something other than what they were originally (i.e. a .htm file before an update is 600, but after and <code>svn update</code>, it gets set to 755, or even 777).</p> <p>What is the easiest way to bypass subversion's attempts at updating the file permissions and ownership? Is there something that can be done within the svn client, or on the Linux server to retain the original file permissions? I'm running RHEL5 (and now 6 on a few select instances).</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USP̲̳x͓L̳
    1. USScott
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAvoid having subversion modify Linux file permissions.
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAvoid having subversion modify Linux file permissions.
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAvoid having subversion modify Linux file permissions.
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload