07cf7fedfe
...otherwise 'gitolite help' was getting too confusing, mixing up stuff that users should not be running directly (even on the server) ---- implementation notes: those who are worried about the '../triggers/' in various parts of the code here, remember you can only do that from a command line on the server. Remote users can only use commands that have been explicitly listed in the COMMANDS hash in the rc file. This means they can't even access other commands in the same directory as, say, the 'info' command, so a '../' is definitely not going to work. |
||
|---|---|---|
| .. | ||
| keys | ||
| 0-me-first.t | ||
| access.t | ||
| all-yall.t | ||
| basic.t | ||
| branch-perms.t | ||
| daemon-gitweb-via-perms.t | ||
| deleg-1.t | ||
| deleg-2.t | ||
| deny-create.t | ||
| deny-rules-2.t | ||
| deny-rules.t | ||
| easy.t | ||
| git-config.t | ||
| gitolite-receive-pack | ||
| gitolite-upload-pack | ||
| glt | ||
| include-subconf.t | ||
| info.t | ||
| invalid-refnames-filenames.t | ||
| listers.t | ||
| merge-check.t | ||
| perm-roles.t | ||
| perms-groups.t | ||
| personal-branches.t | ||
| README | ||
| reset | ||
| rule-seq.t | ||
| sequence.t | ||
| ssh-authkeys.t | ||
| ssh-basic.t | ||
| vrefs-1.t | ||
| vrefs-2.t | ||
| wild-1.t | ||
| wild-2.t | ||
| writes.t | ||
| z-end.t | ||
WARNING: THE TEST SUITE DELETES STUFF FIRST!
Testing gitolite3 is now one command after the clone:
prove
But because it starts by cleaning the slate, it's best to do it on a spare
userid that you are ok to lose data on.