aboutsummaryrefslogtreecommitdiff
path: root/doc/setup
diff options
context:
space:
mode:
authorMartian <Martian@web>2016-06-22 11:35:48 -0400
committeradmin <admin@branchable.com>2016-06-22 11:35:48 -0400
commit4f89d1f3cb043f8029e847d58ee6d0926288e7bb (patch)
tree0be24f301dad1b7fd8575f3bf0a56cc7f6bbcd7f /doc/setup
parent75438e12e563f2bd3f21d3a4943a3c83656eeb97 (diff)
downloadikiwiki-4f89d1f3cb043f8029e847d58ee6d0926288e7bb.tar
ikiwiki-4f89d1f3cb043f8029e847d58ee6d0926288e7bb.tar.gz
Diffstat (limited to 'doc/setup')
-rw-r--r--doc/setup/byhand/discussion.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/setup/byhand/discussion.mdwn b/doc/setup/byhand/discussion.mdwn
index 6fc931ad3..deb79a8db 100644
--- a/doc/setup/byhand/discussion.mdwn
+++ b/doc/setup/byhand/discussion.mdwn
@@ -18,3 +18,5 @@ One possible thing is security: Is it just a precaution or would anyone with "wr
> to commit directly to the VCS, would be able to replace it. That breaks ikiwiki's
> security model, because replacing the setup file is sufficient to achieve
> arbitrary code execution as the user running the CGI and VCS hooks. --[[smcv]]
+
+>> Thanks. After all found it here: [[security]]. Now I wonder if I always use a file from the master branch, while limiting users to staging, it might fly...