Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>From your description in the comments it seems that the problem is that your <code>apache</code> user cannot write to the repository, which is clearly required when you use <code>git pull</code>. You have two courses of action:</p> <ol> <li>Setup up Apache to run the script as another user (e.g. using <a href="http://httpd.apache.org/docs/2.0/suexec.html" rel="nofollow noreferrer">suEXEC</a> either <a href="http://httpd.apache.org/docs/2.0/suexec.html#usage" rel="nofollow noreferrer">on a VirtualHost or via userdir</a>)</li> <li>Change the permissions on your repository so the <code>apache</code> user can write to it</li> </ol> <p>You should think carefully about the security implications of either choice, but the second option is probably easiest. If you don't already have such a group, you can create it with:</p> <pre><code>addgroup gitwriters </code></pre> <p>... and then add yourself and the Apache user to this group:</p> <pre><code>adduser [yourusername] gitwriters adduser apache gitwriters </code></pre> <p>Then you can follow the instructions in <a href="https://stackoverflow.com/questions/3242282/how-to-configure-an-existing-git-repo-to-be-shared-by-a-unix-group">another question</a> to change the permissions on the repository. To reiterate those with some slight variations:</p> <pre><code># Recursively, set the group ownership of every file and directory of your repository: chgrp -R gitwriters /path/to/your/repo # Recursively, make every file and directory of your repository readable and writable # by the group: chmod -R g+rw /path/to/your/repo # Recursively, set the setgid of every directory in the repository. The setgid bit # on directories means that files created in the directory will have the same group # ownership as the directory. find /path/to/your/repo -type d -print0 | xargs -0 chmod g+s </code></pre> <p>Then hopefully your <code>git pull</code> should work.</p>
    singulars
    1. This table or related slice is empty.
    1. POshell_exec and git pull
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USMark Longair
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POshell_exec and git pull
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCheers Mark for your help on this. I've followed what you said, currently I have this: `ip-xx-xxx-xx-xxx ~: id apache uid=48(apache) gid=48(apache) groups=48(apache),10(wheel),501(gitwriters)` However when executing `git pull` it's still being run as apache under apache group.. Is there way to alter the default group - if that makes sense! Apologies, quite new to all this, cheers again.
      singulars
      1. PO
      1. USwilliamsowen
    2. CO@williamsowen: Yes, if you've followed approach 2, you're not changing the user that the PHP code is being run as, you're just making that user (as well as your usual user account) able to write to the repository. Do you definitely need to have it running as a different user? If so, you'll need to look into approach 1.
      singulars
      1. PO
      1. USMark Longair
 

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