User Tools

Site Tools

Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
developer_installation [2019/10/05 13:53] – [The User Privileges Issue] Introduce $REPOSITORY. Traumflugdeveloper_installation [2019/10/05 14:03] (current) – [The User Privileges Issue] Hint for Git repos. Traumflug
Line 32: Line 32:
  
 At this point the situation is that the sources are owned by the developer, while they're about to get handled by the web server user. Running a shop includes file creations by the web server, which has no privileges to do so in developer-owned directories. At this point the situation is that the sources are owned by the developer, while they're about to get handled by the web server user. Running a shop includes file creations by the web server, which has no privileges to do so in developer-owned directories.
 +
 +For installations in a Git repository, one should move //.git// aside first, see [[Github Best Practices#File Permissions|Github Best Practices]].
  
 To solve this conflict, extended Access Control Lists (ACLs) come to the rescue. Setting this up looks a bit complicated, but it has to be done only once. For more details, see the [[https://git.wiki.kernel.org/index.php/Git_FAQ#How_do_I_share_a_Git_repository_using_POSIX_ACLs.3F|Git Wiki]]. Here we can simply copy & paste (except for the second line): To solve this conflict, extended Access Control Lists (ACLs) come to the rescue. Setting this up looks a bit complicated, but it has to be done only once. For more details, see the [[https://git.wiki.kernel.org/index.php/Git_FAQ#How_do_I_share_a_Git_repository_using_POSIX_ACLs.3F|Git Wiki]]. Here we can simply copy & paste (except for the second line):
developer_installation.txt · Last modified: 2019/10/05 14:03 by Traumflug