| 1 |
[[!comment format=mdwn |
| 2 |
username="klml" |
| 3 |
ip="188.174.93.195" |
| 4 |
subject="comment 2" |
| 5 |
date="2012-04-16T19:57:20Z" |
| 6 |
content=""" |
| 7 |
hi smcv, |
| 8 |
|
| 9 |
> when a page is viewed, the web server serves the compiled HTML without IkiWiki being involved. |
| 10 |
|
| 11 |
yes you are right, but I still think its a feature ;) |
| 12 |
|
| 13 |
> 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. |
| 14 |
|
| 15 |
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. |
| 16 |
|
| 17 |
thx |
| 18 |
klml |
| 19 |
|
| 20 |
"""]] |