Moving architecture to piny-code.

4 files changed, 4 insertions, 41 deletions

diff --git a/architecture/features.mdwn b/architecture/features.mdwn
index fbdedb2..060309a 100644
--- a/architecture/features.mdwn
+++ b/architecture/features.mdwn
@@ -1,7 +1 @@
-An in-distributed-repo model for
-
-- code
-- blogs
-- bugs
-- web pages
-- [[mail]]
+[moved here](/piny-code/architecture/feature)
diff --git a/architecture/mail.mdwn b/architecture/mail.mdwn
index 61bbfcd..a6fe0e2 100644
--- a/architecture/mail.mdwn
+++ b/architecture/mail.mdwn
@@ -1,6 +1 @@
-I can presumably get mailing lists into ikiwiki using one of the following:
-
-- MLM+Ikiwiki [comment-by-mail plugin](http://ikiwiki.info/todo/comment_by_mail/)
-- MLM+Ikiwiki [mailbox plugin](http://pivot.cs.unb.ca/git/?p=ikimailbox.git;a=summary)
-
-But how would we get it into git? Might we have to do that externally?
+[moved here](/piny-code/architecture/mail)
diff --git a/architecture/needed_admin_infrastructure.mdwn b/architecture/needed_admin_infrastructure.mdwn
index 7591b96..269a65a 100644
--- a/architecture/needed_admin_infrastructure.mdwn
+++ b/architecture/needed_admin_infrastructure.mdwn
@@ -1,5 +1 @@
-- DONE: HTTP AUTH from PAM through the magic of mod-auth-pam
-- DONE: HTTP access from /etc/group through the magic of mod-auth-sys-group
-- DONE: Shell security through rbash and privilege escalation security (for mkwiki, mkuser, etc) through sudo
-- DONE: Guaranteed namespace coherence with the vhosting of cgi, secure, and normal with the aid of a wildcard SSL certificate
-- TODO: Work out how to pass mailing list emails around. Probably either ssh or vserver namespace magic.
+[moved here](/piny-code/architecture/needed_admin_infrastructure)
diff --git a/architecture/needed_user_facing_infrastructure.mdwn b/architecture/needed_user_facing_infrastructure.mdwn
index 2729859..74c5fc8 100644
--- a/architecture/needed_user_facing_infrastructure.mdwn
+++ b/architecture/needed_user_facing_infrastructure.mdwn
@@ -1,23 +1 @@
-TODO: user-facing documentation on piny-web
-
-It'd be nice to maintain feature parity between command line access and web access.
-
-[[!table data="""
-feature				|command line						|web
-anonymous account creation	|DONE: ssh createuser@piny.be				|TODO: CGI frontend to adduser
-password modification		|DONE: /srv/rbin/passwd					|TODO: Authen::PAM chauthtok CGI jblake: the pam interface was *really* not designed with http in mind though if you hard-code the interaction script it's not hard at all
-repo creation, deletion		|DONE: /srv/rbin/newrepo, rmrepo, TODO: lsrepo		|TODO: CGI frontend
-repo user management		|DONE: /srv/rbin/addaccess, rmaccess TODO: lsaccess	|TODO: CGI frontend
-[[mailing list addition|mail]]	|TODO: ssh piny /srv/rbin/addlist			|TODO: CGI frontend
-authorized_keys modification	|TODO: cmdlind frontend to cat > ~/.ssh/authorized_keys	|TODO: CGI frontend, though i am not convinced anyone would care
-config tweaking			|TODO: ssh piny /srv/rbin/chrepo			|TODO: CGI frontend
-commit access			|DONE: git+ssh://piny/srv/whatever.git			|DONE: Ikiwiki+mod-auth-sys-group/mod-auth-pam, though I am told there is a magic hook to allow public editing through git://
-"""]]
-
-Needed config tweakables
-
-- TODO: globally writable repos vs. group writable repos
-- TODO: globally readable repos vs. group readable repos
-- TODO: ikiwiki-editable vs. git-only
-- TODO: editable ikiwiki templates vs. default layout
-- TODO: user-configured domain vs. default piny domain
+[moved here](/piny-code/architecture/needed_user_facing_infrastructure)