1 |
<html> |
2 |
<body> |
3 |
|
4 |
<pre> |
5 |
o check out from cvs-repository: |
6 |
o joko/doc -> /home/joko/public_html/computing/overview/topics/ |
7 |
o leaded to (A): |
8 |
o write mini-howto: "howto use, document and enhance the '.cvslink'-symlinking-mechanism" |
9 |
o introduce command to 'tiki-workflow|tiki-publish' |
10 |
x introduced '.cvs'-interface (directory-style) |
11 |
x now directly accessible (but hidden) via http://netfrag.org/~joko/computing/overview/topics/.cvs/ |
12 |
x here: made public by adding a "README.html" (or "HEADER.html") which either: |
13 |
x includes a html-link (a-tag) to './.cvs' |
14 |
o makes a redirect via meta-tags or javascript |
15 |
o leads to (B): |
16 |
o start 'home2web': |
17 |
x begin with having an overview of the recent topics stored in cvs |
18 |
x continue by expanding this topic-list through more details |
19 |
x use mechanisms delivered from Apache |
20 |
x HEADER.html, README.html |
21 |
x php: http-redirect |
22 |
o add more links! |
23 |
o fix proposals of how links should be expanded (maybe post RFC to news.netfrag.org first? -> create newsgroup 'nfo.rfc') |
24 |
x manually? no! (hmmm, grrrr......) |
25 |
o pod? for now! |
26 |
o DocBook? not yet! |
27 |
o some wiki? why not? |
28 |
o add links to internal tools (e.g. TUTOS, chora, etc.) |
29 |
o add external links |
30 |
o add co-worker topics |
31 |
o leads to (C): |
32 |
o write mini-howto: web publishing with cvs |
33 |
- write in pod |
34 |
- commit to cvs |
35 |
- checkout from cvs |
36 |
- build html from pod |
37 |
- publish html |
38 |
x do that regularly / in interval: use cron! |
39 |
su joko |
40 |
cd ~ |
41 |
nano .cronrc-hourly |
42 |
add line(s): [...] cvs update topics [...] |
43 |
crontab -e |
44 |
add line: * 1 * * * ~/.cronrc-hourly |
45 |
o post message "About" (this) to announce@news.netfrag.org |
46 |
</pre> |
47 |
|
48 |
</body> |
49 |
</html> |