changelog shortlog tags branches files raw gz bz2 help

Mercurial > hg > werc / changeset: Documentation updates:

changeset 651: fce7c8747d57
parent 650: 275899147886
child 652: 1b95f0539231
author: Uriel <u@berlinblue.org>
date: Tue, 28 Jun 2011 01:50:24 +0000
files: README etc/initrc sites/default.cat-v.org/_werc/lib/headers.inc sites/werc.cat-v.org/development/todo.md sites/werc.cat-v.org/docs/config-options.md
description: Documentation updates:
- Try to explain better that werc expects Plan 9 tools in /usr/local/plan9/bin/
- Note possible bug.
- Other small doc changes.
     1.1--- a/README	Sat Feb 05 16:50:47 2011 +0000
     1.2+++ b/README	Tue Jun 28 01:50:24 2011 +0000
     1.3@@ -13,8 +13,14 @@
     1.4 
     1.5 Requirements:
     1.6 
     1.7+* An http server that can handle CGIs
     1.8 * Plan 9 from User Space: http://plan9.us - Or 9base-5 or later: http://tools.suckless.org/9base
     1.9-* An http server that can handle CGIs
    1.10+
    1.11+Note: Werc by default expects the Plan 9 tools to be installed under
    1.12+/usr/local/plan9/bin/, if you have installed them elsewhere you will need to
    1.13+edit the #! line in bin/werc.rc and customize the $plan9port variable in your
    1.14+etc/initrc.local.
    1.15+
    1.16 
    1.17 Instructions:
    1.18 
     2.1--- a/etc/initrc	Sat Feb 05 16:50:47 2011 +0000
     2.2+++ b/etc/initrc	Tue Jun 28 01:50:24 2011 +0000
     2.3@@ -14,6 +14,9 @@
     2.4 # If you use 9base, it should point to your 9base root, try for example:
     2.5 #plan9port=/usr/lib/9base # This is the default 9base install path in Debian.
     2.6 
     2.7+# If rc is not installed as /usr/local/plan9/bin/rc you will also need to change
     2.8+# the #! line in bin/werc.rc!
     2.9+
    2.10 # Path, make sure the plan9port /bin directory is included before /bin
    2.11 # Keep '.' in path! It is needed.
    2.12 path=($plan9port/bin . ./bin ./bin/contrib /bin /usr/bin)
     3.1--- a/sites/default.cat-v.org/_werc/lib/headers.inc	Sat Feb 05 16:50:47 2011 +0000
     3.2+++ b/sites/default.cat-v.org/_werc/lib/headers.inc	Tue Jun 28 01:50:24 2011 +0000
     3.3@@ -2,3 +2,4 @@
     3.4 <meta name="google-site-verification" content="z5zCyEitNLNZmhVblsogrEiy6Acf0UZROsFMtLjioN4" />
     3.5 <META name="y_key" content="49dff3fad5352458"><META name="y_key" content="5dc40bfee9494e98"><META name="y_key" content="b60a53d1fa98f4c8">
     3.6 <meta name="msvalidate.01" content="5008C6E6B172BEB1F43E770296C3D560" />
     3.7+<meta name="alexaVerifyID" content="l1vBNiKWqe9hCZhp0jV8OKPyjps" />
     4.1--- a/sites/werc.cat-v.org/development/todo.md	Sat Feb 05 16:50:47 2011 +0000
     4.2+++ b/sites/werc.cat-v.org/development/todo.md	Tue Jun 28 01:50:24 2011 +0000
     4.3@@ -60,6 +60,7 @@
     4.4 Similar frameworks to be investigated and mined for good ideas to steal:
     4.5 
     4.6   * TinyTim: http://www.reddit.com/r/programming/duplicates/dbaee/
     4.7+  * nanoblogger: http://nanoblogger.sourceforge.net/
     4.8 
     4.9 
    4.10 Known Bugs
    4.11@@ -69,6 +70,11 @@
    4.12 * 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.
    4.13 * Links in Blagh feeds become confused if markdown 'references' are used, markdown references suck, but I guess we need to address this somehow... 
    4.14 * 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.
    4.15+* .md files of the following form, without a new line after the last = seem to cause problems in some setups:
    4.16+
    4.17+    Foo Bar
    4.18+    =======
    4.19+
    4.20 
    4.21 
    4.22 Fixed or WFM Bugs
     5.1--- a/sites/werc.cat-v.org/docs/config-options.md	Sat Feb 05 16:50:47 2011 +0000
     5.2+++ b/sites/werc.cat-v.org/docs/config-options.md	Tue Jun 28 01:50:24 2011 +0000
     5.3@@ -52,9 +52,17 @@
     5.4 
     5.5 The permissions system is very flexible, for example to only allow access to members of the group 'editors' you can do something like:
     5.6 
     5.7-    if(! check_user editors)
     5.8-        perm_redirect /_users/login
     5.9+    switch ($req_path) {
    5.10+    case /_users/login
    5.11+    case /pub/*
    5.12+    case /robots.txt
    5.13+    case *
    5.14+        if(! check_user editors)
    5.15+                perm_redirect /_users/login
    5.16+    }
    5.17+
    5.18 
    5.19 To automatically redirect users without permission to the login page if they are not members of the group 'editors'.
    5.20 
    5.21 See also [the documentation on user and group management](user_management).
    5.22+