summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2016-12-18 15:10:17 +0100
committerRichard Maw <richard.maw@gmail.com>2017-01-02 18:25:52 +0000
commit557135fa79d402ca53dbaf8f3f79ca207688c720 (patch)
treefd301e55b608cf66327be3438d44f673bcd43d60 /doc
parentc359dcf4a2e199d163a7ce6ad093edb0ad4d554e (diff)
downloadgitano-557135fa79d402ca53dbaf8f3f79ca207688c720.tar.gz
Drop chapters/sections I don't have time to write
Diffstat (limited to 'doc')
-rw-r--r--doc/admin/000.mdwn63
1 files changed, 25 insertions, 38 deletions
diff --git a/doc/admin/000.mdwn b/doc/admin/000.mdwn
index 929d8d5..c46ed52 100644
--- a/doc/admin/000.mdwn
+++ b/doc/admin/000.mdwn
@@ -98,8 +98,31 @@ soon.
# Repository management
-FIXME. This chapter discusses repository management, including
-repository config variables.
+Repositories are managed using commands in the nearby table. Use the
+Gitano `help` command to get details.
+
+------- ---------------------------------------------------
+command description
+`create` create a new, empty repository
+`destroy` destroy a repository
+`copy` create a new repoistory by copying an existing one
+`config` inspect or set repository configurtion
+------- ---------------------------------------------------
+
+Configuration variables for repositories are listed in a table.
+
+------- ---------------------------------------------------
+variable description
+`project.description` description of repo, shown by web interface
+`project.head` where the repository HEAD points, e.g., `refs/heads/master`
+`project.owner` Gitano user who owns the repository
+------- ---------------------------------------------------
+
+FIXME: Are there more?
+
+You can set any configuration varible, but the `project.*` ones have
+special meaning to Gitano.
+
# Lace syntax and semantics
@@ -280,40 +303,6 @@ follows:
FIXME: What about per-project rules?
-## Testing one's ruleset
-
-META: This section discusses systematic testing of one's ruleset.
-Might or might not include automated testing (with yarn).
-
-# The default Gitano ruleset
-
-META: This chapter is a walkthrough of the default Gitano ruleset.
-Ideally implemented in such a way that it is either generated from the
-Gitano source code, or vice versa.
-
-# Good practices for writing rulesets
-
-META: This chapter discusses various best practices for writing Gitano
-rulesets. It may initially have to be a skeleton until the Gitano
-community gathers enough experience to write something substantial.
-But an interview with Daniel for good ideas should come up with enough
-for an initial chapter.
-
-# Common things one may want to do
-
-META: This chapter discusses some common changes one may want to do to
-the default ruleset. Ideally, there would be none, but reality is ugly.
-
-## Anonymous access
-
-META: This section describes how to allow anyone access to specific
-repositories.
-
-## Cgit integration
-
-META: This section describes how to allow cgit show specific
-repositories.
-
# Backup and restore of a Gitano instance
When gitano-setup is run, the admin needs to specify a Unix user in
@@ -322,5 +311,3 @@ we'll assume the home directory is `/home/git`.
To backup a Gitano instnace, backup `/home/git`. To restore, restore
the directory.
-
-FIXME: Need to re-generate .ssh/authorizes_keys?