aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-12-07 04:58:32 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-12-07 04:58:32 +0000
commit607dcf0f24bfdeaa29d77c8d301472fc815e4077 (patch)
treed213a55a74189fc6437043fcc29ff56518af5260
parente1604375da59fc236068b71c83df2748dd638aa9 (diff)
downloadikiwiki-607dcf0f24bfdeaa29d77c8d301472fc815e4077.tar
ikiwiki-607dcf0f24bfdeaa29d77c8d301472fc815e4077.tar.gz
response
-rw-r--r--doc/index/discussion.mdwn7
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn
index fa869aaba..3d80d0995 100644
--- a/doc/index/discussion.mdwn
+++ b/doc/index/discussion.mdwn
@@ -32,6 +32,11 @@ something, that I think is very valuable.
>> and then route all page views through ikiwiki.cgi. Am I missing something?
>> --[[Ethan]]
+>>> Or you could just use apache or whatever and set up the access controls
+>>> there. Of course, that wouldn't integrate very well with the wiki,
+>>> unless perhaps you decided to use http basic authentication and the
+>>> httpauth plugin for ikiwiki that integrates with that.. [[--Joey]]
+
----
Some questions about the RecentChanges function. -- Ethan
@@ -63,4 +68,4 @@ with all news or the one with the latest news only, I don't know yet.)
>> That wouldn't use the same style for the RSS and Atom links, and it
>> wouldn't embed the feed link into `<head>` so that browsers can automatically
->> find it. \ No newline at end of file
+>> find it.