doc/topics/home2web.html

<html>
<body>

<pre>

o check out from cvs-repository:
  o joko/doc -> /home/joko/public_html/computing/overview/topics/
  o leaded to (A):
    o write mini-howto: "howto use, document and enhance the '.cvslink'-symlinking-mechanism"
    o introduce command to 'tiki-workflow|tiki-publish'
    x introduced '.cvs'-interface (directory-style)
      x now directly accessible (but hidden) via http://netfrag.org/~joko/computing/overview/topics/.cvs/
      x here: made public by adding a "README.html" (or "HEADER.html") which either:
        x includes a html-link (a-tag) to './.cvs'
        o makes a redirect via meta-tags or javascript
  o leads to (B):
    o start 'home2web':
      x begin with having an overview of the recent topics stored in cvs
      x continue by expanding this topic-list through more details
         x use mechanisms delivered from Apache
            x HEADER.html, README.html
            x php: http-redirect
      o add more links!
        o fix proposals of how links should be expanded (maybe post RFC to news.netfrag.org first? -> create newsgroup 'nfo.rfc')
          x manually? no! (hmmm, grrrr......)
          o pod? for now!
          o DocBook? not yet!
          o some wiki? why not?
        o add links to internal tools (e.g. TUTOS, chora, etc.)
        o add external links
      o add co-worker topics
  o leads to (C):
    o write mini-howto: web publishing with cvs
       - write in pod
       - commit to cvs
       - checkout from cvs
       - build html from pod
       - publish html
  x do that regularly / in interval: use cron!
      su joko
      cd ~
      nano .cronrc-hourly
      add line(s): [...]  cvs update topics  [...]
      crontab -e
      add line: 07 * * * * ~/.cronrc-hourly
  o post message "About" (this) to announce@news.netfrag.org

</pre>

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