ansaurus

Question

Answer 1

+2 A:

It looks like you have a local permission problem. There is nothing specific to Git about this problem. The hierarchy could contain anything and these instructions would be exactly the same. By default, Git will honor the umask setting that is described later (unless it is overridden by a core.sharedRepository configuration).

In your comments you said that your user will be the one updating the contents of the hierarchy and you will also have a web server that will be reading the contents of the hierarchy. I will assume that the web server is running under some other user (this usually the case (e.g. Apache running as user httpd)). Further, I will assume that is acceptable if other users on this same machine can also read the contents of the hierarchy (the required permission scheme for such a configuration is more complicated—it involves using a special group and making sure your files and directories have that group as their ‘group owner’).

Facts

The hierarchy of concern is rooted at: /opt/lammp/htdocs/myProject
Local user dan needs to be able modify the contents of the hierarchy at will.
A web server (probably running as some other user) needs to be able to read the contents of the hierarchy.
It is OK if other users on the local machine can read the contents of the hierarchy.

Solution

Have dan be the ‘user owner’ of all of the hierarchy. The ‘group owner’ is not important.
Give the ‘user owner’ (dan) read, write, and execute permissions for directories and at least read, and write permissions for files (some file may be executable if (e.g.) they are scripts).
Give the ‘group owner’ the same permissions as the ‘user’ owner, but without write permission.
Give all ‘other’ users the same permissions as the ‘user’ owner, but without write permission.

Implementation

Initial Setup

Make dan the owner of all of the hierarchy.
- As any user that that can “sudo to root” (or run in a root shell without sudo):
```
someuser$ sudo chown -R dan /opt/lammp/htdocs/myProject
```
Give everyone read permission (and also execute permission for all directories and all files that already are executable by someone; any write permissions are stripped). Additionally, give dan write permission.
- As dan (note the lack of sudo!):
```
dan$ chmod -R a-st=rX,u+w /opt/lammp/htdocs/myProject
```
This will strip the setuid/setgid/sticky bits and give directories and executables mode 755 and all other files mode 644.

Ongoing Usage

To make sure that new files are readable but not writable (by default) by others (e.g. the web server user), you should set your umask when working in this directory.

dan$ umask 022

This masks off the ‘group’ and ‘other’ write permission for new files and directories, but leaves read and execute alone.

If you forget to use this and your default umask is more restrictive (or less restrictive), then you will need to re-run the (non-sudo!) chmod command from the “Initial Setup” section. It will reset any permissions that are too strict (or too loose).

Chris Johnsen 2010-03-09 04:42:58

Thank you! after much (blind) googling, your steps above solved my problem. Good man!

superjadex12 2010-07-13 08:50:14

ansaurus

tags:

views:

answers:

Problems with first upload to github

Facts

Solution

Implementation

Initial Setup

Ongoing Usage

related questions