aboutsummaryrefslogtreecommitdiff
path: root/doc/forum/access_restrictions:_for_extranet/comment_2_563040aa099c9366dc5701eb4bc9c10d._comment
blob: 75b9d49bca909dd9267e55a7816a97314b645518 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
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

"""]]