Documentation updates:

- Try to explain better that werc expects Plan 9 tools in /usr/local/plan9/bin/
- Note possible bug.
- Other small doc changes.
This commit is contained in:
Uriel 2011-06-28 01:50:24 +00:00
parent 18032ba244
commit 3d2b2ea2d7
5 changed files with 27 additions and 3 deletions

8
README
View File

@ -13,8 +13,14 @@ Installation
Requirements: Requirements:
* Plan 9 from User Space: http://plan9.us - Or 9base-5 or later: http://tools.suckless.org/9base
* An http server that can handle CGIs * An http server that can handle CGIs
* Plan 9 from User Space: http://plan9.us - Or 9base-5 or later: http://tools.suckless.org/9base
Note: Werc by default expects the Plan 9 tools to be installed under
/usr/local/plan9/bin/, if you have installed them elsewhere you will need to
edit the #! line in bin/werc.rc and customize the $plan9port variable in your
etc/initrc.local.
Instructions: Instructions:

View File

@ -14,6 +14,9 @@ plan9port=$PLAN9
# If you use 9base, it should point to your 9base root, try for example: # If you use 9base, it should point to your 9base root, try for example:
#plan9port=/usr/lib/9base # This is the default 9base install path in Debian. #plan9port=/usr/lib/9base # This is the default 9base install path in Debian.
# If rc is not installed as /usr/local/plan9/bin/rc you will also need to change
# the #! line in bin/werc.rc!
# Path, make sure the plan9port /bin directory is included before /bin # Path, make sure the plan9port /bin directory is included before /bin
# Keep '.' in path! It is needed. # Keep '.' in path! It is needed.
path=($plan9port/bin . ./bin ./bin/contrib /bin /usr/bin) path=($plan9port/bin . ./bin ./bin/contrib /bin /usr/bin)

View File

@ -2,3 +2,4 @@
<meta name="google-site-verification" content="z5zCyEitNLNZmhVblsogrEiy6Acf0UZROsFMtLjioN4" /> <meta name="google-site-verification" content="z5zCyEitNLNZmhVblsogrEiy6Acf0UZROsFMtLjioN4" />
<META name="y_key" content="49dff3fad5352458"><META name="y_key" content="5dc40bfee9494e98"><META name="y_key" content="b60a53d1fa98f4c8"> <META name="y_key" content="49dff3fad5352458"><META name="y_key" content="5dc40bfee9494e98"><META name="y_key" content="b60a53d1fa98f4c8">
<meta name="msvalidate.01" content="5008C6E6B172BEB1F43E770296C3D560" /> <meta name="msvalidate.01" content="5008C6E6B172BEB1F43E770296C3D560" />
<meta name="alexaVerifyID" content="l1vBNiKWqe9hCZhp0jV8OKPyjps" />

View File

@ -60,6 +60,7 @@ Future Plansi and Blue Sky
Similar frameworks to be investigated and mined for good ideas to steal: Similar frameworks to be investigated and mined for good ideas to steal:
* TinyTim: http://www.reddit.com/r/programming/duplicates/dbaee/ * TinyTim: http://www.reddit.com/r/programming/duplicates/dbaee/
* nanoblogger: http://nanoblogger.sourceforge.net/
Known Bugs Known Bugs
@ -69,6 +70,11 @@ Known Bugs
* If a dir under apps/ doesn't contain an app.rc file, werc fails to start. A possible fix would be to replace $werc_apps default with `apps/*/app.rc` instead of `apps/*/`, this would be backwards incompatible, but I doubt anyone uses that option. * If a dir under apps/ doesn't contain an app.rc file, werc fails to start. A possible fix would be to replace $werc_apps default with `apps/*/app.rc` instead of `apps/*/`, this would be backwards incompatible, but I doubt anyone uses that option.
* Links in Blagh feeds become confused if markdown 'references' are used, markdown references suck, but I guess we need to address this somehow... * Links in Blagh feeds become confused if markdown 'references' are used, markdown references suck, but I guess we need to address this somehow...
* Somewhat similarly to the abouve, relative urls in imgs, links, etc. can easily break when used in Blagh posts, so it is not all markdown's fault. * Somewhat similarly to the abouve, relative urls in imgs, links, etc. can easily break when used in Blagh posts, so it is not all markdown's fault.
* .md files of the following form, without a new line after the last = seem to cause problems in some setups:
Foo Bar
=======
Fixed or WFM Bugs Fixed or WFM Bugs

View File

@ -52,9 +52,17 @@ Access Control and Permissions
The permissions system is very flexible, for example to only allow access to members of the group 'editors' you can do something like: The permissions system is very flexible, for example to only allow access to members of the group 'editors' you can do something like:
switch ($req_path) {
case /_users/login
case /pub/*
case /robots.txt
case *
if(! check_user editors) if(! check_user editors)
perm_redirect /_users/login perm_redirect /_users/login
}
To automatically redirect users without permission to the login page if they are not members of the group 'editors'. To automatically redirect users without permission to the login page if they are not members of the group 'editors'.
See also [the documentation on user and group management](user_management). See also [the documentation on user and group management](user_management).