Mercurial > hg > chronicle
comparison COMMENTS @ 109:10797bf26799
Added 'COMMENTS' to the file.
author | Steve Kemp <steve@steve.org.uk> |
---|---|
date | Thu, 13 Dec 2007 12:18:20 +0000 |
parents | |
children | b296489d9ea1 |
comparison
equal
deleted
inserted
replaced
108:a25099606ec5 | 109:10797bf26799 |
---|---|
1 | |
2 | |
3 Chronicle, since version 2.0, supports the submission of post | |
4 comments. | |
5 | |
6 The way this works is rather non-standard so please read this | |
7 document to understand it. | |
8 | |
9 | |
10 Basic Usage | |
11 ----------- | |
12 | |
13 The basic use of chronicle is to convert a collection of text files | |
14 into a HTML & RSS blog. | |
15 | |
16 Generally it appears that people will do this upon a local machine, | |
17 then scp, rsync, or otherwise move the output into place upon their | |
18 remote webserver. | |
19 | |
20 This process looks something like this: | |
21 | |
22 chronicle --input=./blog --output=./html | |
23 rsync html user@host:/path/to/blog | |
24 | |
25 | |
26 Advanced Usage | |
27 -------------- | |
28 | |
29 Since the blog, once produced, is typically stored upon a remote | |
30 system there is no easy way for comments which are stored upon that | |
31 system to be integrated into the main blog. | |
32 | |
33 The solution to this problem is to merely record comments upon | |
34 the webserver in simple text files. | |
35 | |
36 Later these can be fetched to the machine which is building the | |
37 blog, and integrated for the next rebuild: | |
38 | |
39 | |
40 scp uesr@host://path/to/comments/* ./comments/ | |
41 chronicle --input=./blog --output=./html --comments=./comments | |
42 rsync html user@host:/path/to/blog | |
43 | |
44 | |
45 Steve | |
46 -- |