Databases
StackOverflow2013
Postsdbo
POGit post receive hook with sudo -u not working for some users
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGit post receive hook with sudo -u not working for some users
    primarykey
    data
    text
    <p>We have a website we're developing with WP-Engine. To simplify the processes I've set up the git repository for the site to automatically push code changes up to the WP-Engine staging area, using a Post Receive hook that looks like this:</p> <pre><code>#!/bin/bash -x PUSH_AS_USER="admin" sudo -u $PUSH_AS_USER git push wp-engine-staging master </code></pre> <p>I've also made it so that any user in the admin group, can sudo -u admin git, without typing the password (for reference, add the following to /etc/sudoers</p> <pre><code>%admin ALL=(admin) NOPASSWD: /usr/bin/git` </code></pre> <p>When I push to the repository, it fires the post commit hook no problem, however for some reason it only works for me. Two other users get the following warning:</p> <pre><code>[username@server repository]$ sudo -u admin git push wp-engine-staging master fatal: unable to access '/home/username/.config/git/config': Permission denied </code></pre> <p>The weird thing is, I don't have this file for my user and mine works ok. Additionally, if I create the file for those users, I can't seem to give admin permission to view it, even if I add admin to the users own group, and give read permission to the group in every directory to the file. (ie, /home/username/.config/git/ and the config file itself).</p> <p>As another example of this weird issue:</p> <pre><code>[daniel@server repository]$ sudo su username [username@server repository]$ sudo -u admin git config --global --list fatal: unable to access '/home/username/.config/git/config': Permission denied [username@server repository]$ exit [daniel@server repository]$ sudo -u admin git config --global --list user.email=daniel@example.com user.name=Daniel [daniel@server repository]$ cat /home/daniel/.config/git/config cat: /home/daniel/.config/git/config: No such file or directory </code></pre> <p>It's rather messing with our workflow. Any ideas?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjasonleonhard
    1. USDanielM
    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. This table or related slice is empty.
    1. VO
      singulars
      1. POGit post receive hook with sudo -u not working for some users
      1. USDanielM
      1. VTFavorite
    2. VO
      singulars
      1. POGit post receive hook with sudo -u not working for some users
      1. This table or related slice is empty.
      1. VTUpMod
    1. COObviously it has something to do with permissions on `.config` or its sub-directory and/or files, but you already checked the obvious. So maybe it's the un-obvious, e.g., SELinux? I gave up on trying to work around SELinux things and turned it off entirely, in various previous-$work-things. :-)
      singulars
      1. POGit post receive hook with sudo -u not working for some users
      1. UStorek
    2. COGood thinking, but in this case we aren't using SELinux. I think I may be looking at two seperate issues here. 1) Git _might_ not be properly set up for the other users (though they can use git when not switching user). 2) When using sudo -u, it's keeping environment variables belonging to the original user. Unfortunately I haven't been able to fix either of these issues either. :)
      singulars
      1. POGit post receive hook with sudo -u not working for some users
      1. USDanielM
 

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