Introduction
Introduction Statistics Contact Development Disclaimer Help
patched the README file in preparation for swerc - swerc - anselm's simpler wer…
git clone git://git.suckless.org/swerc
Log
Files
Refs
README
---
commit 626facbaec515abfaf1eddf7a21907cd71a5b1d4
parent 2a05d86cf3f4b5e418c615b1af26cb4181788ffb
Author: [email protected] <unknown>
Date: Sun, 12 Feb 2012 18:26:08 +0100
patched the README file in preparation for swerc
Diffstat:
M README | 51 +++++++----------------------…
1 file changed, 11 insertions(+), 40 deletions(-)
---
diff --git a/README b/README
@@ -1,12 +1,7 @@
-werc - a minimalist document management system
-----------------------------------------------
-
-Werc is a content management system and web (anti-)framework designed to be si…
-use, simple to setup, simple to hack on, and not get on the way while allowing
-users easy customization.
-
-For more information see the official website: http://werc.cat-v.org/
+swerc - a minimalist document management system
+-----------------------------------------------
+swerc is simple werc, a fork of Uriel's werc at: http://werc.cat-v.org/
Installation
------------
@@ -14,9 +9,9 @@ Installation
Requirements:
* An http server that can handle CGIs
-* Plan 9 from User Space: http://plan9.us - Or 9base-5 or later: http://tools.…
+* Plan 9 from User Space: http://plan9.us - Or http://tools.suckless.org/9base
-Note: Werc by default expects the Plan 9 tools to be installed under
+Note: swerc 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.
@@ -24,7 +19,7 @@ etc/initrc.local.
Instructions:
-Untar werc at your desired location, configure httpd to use
+Untar swerc at your desired location, configure httpd to use
/path-to-your-werc-installation/bin/werc.rc as a cgi-script, it is recommended
that you make werc.rc handle all non-static files (this can be done by setting
it up as your 404 handler) and setup your virtual hosts to handle static files
@@ -42,40 +37,16 @@ standard /usr/local/plan9/ you will need to edit the first …
(Note that p9p is picky about where it is located, once you run ./INSTALL you
should *not* move it to a different directory without running ./INSTALL again.)
-For general configuration options copy etc/initrc to etc/initrc.local and
-customize it as needed. Site (and directory) specific options can be set in a
-sites/example.com/_werc/config file inside the site's directory. To customize
-templates and included files you can store your own version of the files in
-lib/ under sites/example.com/_werc/lib
-
-The source tree for the werc website is included under sites/werc.cat-v.org as
-an example, feel free to use it as a template for your own site.
-
-For more details see the documentation section of the website:
-http://werc.cat-v.org/docs/
-
-
-Contact
--------
-
-For comments, suggestions, bug reports or patches join the werc9 list in
-google groups: http://groups.google.com/group/werc9 or the irc channel #plan9
-in irc.freenode.org
-
-If you have a public website that uses werc I would love to hear about it and
-get feedback about you experience setting it up.
-
-If you want to be notified of new releases see the News section of the website
-or use Freshmeat: http://freshmeat.net/projects/werc/
+For general configuration edit etc/initrc.
+Site (and directory) specific options can be set in a
+sites/example.com/_werc/config file inside the site's directory.
Thanks
------
-Garbeam, Kris Maglione, sqweek, soul9, mycroftiv, maht, yiyus and many others
+Kris Maglione, sqweek, soul9, mycroftiv, maht, yiyus and many others
for their ideas, patches, testing and other contributions.
-
License
-------
-
-Werc is in the public domain.
+swerc is in the public domain.
You are viewing proxied material from suckless.org. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.