Mercurial > hg > chronicle

comparison COMMENTS @ 220:79f30bca8489

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Ran through ispell
author Steve Kemp <steve@steve.org.uk>
date Wed, 16 Apr 2008 19:07:39 +0100
parents 1d4f3be0e000
children 6e34732430db
comparison
equal deleted inserted replaced
219:52326e71a41e 220:79f30bca8489
13 into a HTML & RSS blog. 13 into a HTML & RSS blog.
14 14
15 There are two ways this software is typically used: 15 There are two ways this software is typically used:
16 16
17 Single Machine 17 Single Machine
18 The blog input is stored upon your webserver and you generate 18 The blog input is stored upon your web-server and you generate
19 the output directly to a http-accessible directory upon that 19 the output directly to a http-accessible directory upon that
20 machine. 20 machine.
21 21
22 Multiple Machines 22 Multiple Machines
23 The blog input lives upon one machine, and once you've generated 23 The blog input lives upon one machine, and once you've generated
24 the output you copy it over to a remote webserver where it may 24 the output you copy it over to a remote web-server where it may
25 be viewed. 25 be viewed.
26 26
27 Depending upon which of these ways you use the software the 27 Depending upon which of these ways you use the software the
28 comment support will need to be handled differently. 28 comment support will need to be handled differently.
29 29
30 30
31 31
32 Common Setup 32 Common Setup
33 ------------ 33 ------------
34 34
35 Install the included file cgi-bin/comments.cgi upon the webserver 35 Install the included file cgi-bin/comments.cgi upon the web-server
36 which hosts the blog, and adjust the settings at the start of that 36 which hosts the blog, and adjust the settings at the start of that
37 file to specify: 37 file to specify:
38 38
39 1. The local directory to save the comments within. 39 1. The local directory to save the comments within.
40 40
41 2. The source and destination email addresses to use for notication 41 2. The source and destination email addresses to use for
42 purposes. 42 notification purposes.
43 43
44 44
45 45
46 Single Machine 46 Single Machine
47 -------------- 47 --------------
52 52
53 Assuming you have something like this: 53 Assuming you have something like this:
54 54
55 comments/ 55 comments/
56 A directory to contain the comments. 56 A directory to contain the comments.
57 NOTE: You will need to ensure your webserver has the permissions 57 NOTE: You will need to ensure your web-server has the permissions
58 to save files to this directory. 58 to save files to this directory.
59 59
60 data/ 60 data/
61 The directory where your blog posts are loaded from. 61 The directory where your blog posts are loaded from.
62 62
63 63
64 You may then regenerate your blog via: 64 You may then regenerate your blog via:
65 65
66 chronicle --input=./date/ --comments=./comments/ --output=/var/www/blog/ 66 chronicle --input=./date/ --comments=./comments/ --output=/var/www/blog/
67 67
68 This will ensure that the comments saved by your webserver into the 68 This will ensure that the comments saved by your web-server into the
69 comments directory are included in the (re)generated blog. 69 comments directory are included in the (re)generated blog.
70 70
71 71
72 72
73 73
76 76
77 If you have the blog input files upon machine "local" and the 77 If you have the blog input files upon machine "local" and the
78 hosted blog upon the machine "remote" then you will run into 78 hosted blog upon the machine "remote" then you will run into
79 problems: 79 problems:
80 80
81 1. The comments are saved by your webserver to a local directory 81 1. The comments are saved by your web-server to a local directory
82 upon the machine "remote". 82 upon the machine "remote".
83 83
84 2. To rebuild the blog upon your local machine, "local", you must 84 2. To rebuild the blog upon your local machine, "local", you must
85 have those files. 85 have those files.
86 86