Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You want to set this option on the repository you're pulling into (extract from <code>git help config</code>):</p> <pre><code> core.sharedRepository When group (or true), the repository is made shareable between several users in a group (making sure all the files and objects are group-writable). When all (or world or everybody), the repository will be readable by all users, additionally to being group-shareable. When umask (or false), git will use permissions reported by umask(2). When 0xxx, where 0xxx is an octal number, files in the repository will have this mode value. 0xxx will override user’s umask value (whereas the other options will only override requested parts of the user’s umask value). Examples: 0660 will make the repo read/write-able for the owner and group, but inaccessible to others (equivalent to group unless umask is e.g. 0022). 0640 is a repository that is group-readable but not group-writable. See git-init(1). False by default. </code></pre> <p>To set this option, <code>cd</code> to the working tree or repository that needs to have the right group/mode (not the origin repository you want to pull from), and run <code>git config core.sharedRepository group</code>. It doesn't just set the mode for files in the repository, it also makes sure they are all owned by the group that owns the root of the repository. The option takes effect whether you're working locally in the repository or pushing into it from another repository (e.g. via the <code>git://</code> protocol).</p> <p>If you've already created files in the repository with the wrong owner and/or mode by not having this option set, you'll first need to <code>cd</code> into the repository and run<code>chmod -R g+rw .</code> and <code>chgrp -R www-data .</code> to get it into a consistent state.</p>
    singulars
    1. This table or related slice is empty.
    1. POGit pull with www-data permissions
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDan Hulme
    1. USDan Hulme
    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. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for the answer. The main problem I have with doing that is that I don;t have any access to the git repository itself as it's located on a third parties infrastructure. I am looking at moving this all to GitHub but I don;t know if that will make my life easier or not.
      singulars
      1. PO
      1. USRichard Cleverley
    2. CODon't forget that in Git, every working copy has its own repository: *repository* doesn't mean *upstream*. You only need this setting on the repository that you want to have the right group/mode. You **don't** need to do anything to the origin repository you pull from.
      singulars
      1. PO
      1. USDan Hulme
 

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