diff options
author | Lars Hjemli <hjemli@gmail.com> | 2011-06-18 15:47:20 +0200 |
---|---|---|
committer | Lars Hjemli <hjemli@gmail.com> | 2011-06-18 15:47:20 +0200 |
commit | dc6f7a345acceefa6b74e91bcf8b46f3d8245c71 (patch) | |
tree | 798696880344d97c28704ab3cb3cfe8e8c235bb3 | |
parent | f3d08068d6056e0d2b49cda1e492d87969385e69 (diff) | |
download | cgit-dc6f7a345acceefa6b74e91bcf8b46f3d8245c71.tar.gz cgit-dc6f7a345acceefa6b74e91bcf8b46f3d8245c71.tar.xz |
faq: add entries for permission-related problems
Signed-off-by: Lars Hjemli <hjemli@gmail.com>
-rw-r--r-- | faq | 20 |
1 files changed, 19 insertions, 1 deletions
@@ -1,4 +1,22 @@ Frequently Asked Questions ========================== -(Coming soon) +* I'm using the "scan-path" option, but cgit doesn't find my repo + + * This is most likely due to permission problems: cgit usually runs under + your webserver user account and will need read access to your repo (and + all of the parent directories) + +* My repo shows up in the list of repositories, but when clicking the + repo name, cgit complains that it's "Not a git repository" + + * The most common cause of this is permission problems - see the previous + faq entry for more details. + + * The second most common cause is that you've set repo.path to point + at the working-directory of your git repo - it should point at the + $GITDIR, i.e. the .git directory. + + * A less likely cause is that the repo is, infact, not a valid repo. Try + to run a 'git show' in the offending repo to see if git also reports + about problems. |