urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Added a comment

master
klml 2012-04-16 15:57:20 -04:00 committed by admin
parent 895be9d25e
commit 2015f23052
1 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/forum/access_restrictions:_for_extranet/comment_2_563040aa099c9366dc5701eb4bc9c10d._comment 100644
View File

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="klml"
ip="188.174.93.195"
subject="comment 2"
date="2012-04-16T19:57:20Z"
content="""
hi smcv,
> when a page is viewed, the web server serves the compiled HTML without IkiWiki being involved.
yes you are right, but I still think its a feature ;)
> The best way to integrate access control into IkiWiki would probably be to have a CGI user interface for .htaccess or equivalent - but you'd still have to be careful, because, for instance, if a user can edit public pages, then they can insert a \[[!include]] directive to make the content of a private page public.
My usecase is a website with an small internal area, its just for not \"so public\" files, no private files. And I only have some trusted users.
thx
klml
"""]]