| 1 |
|
<html> |
| 2 |
|
<body> |
| 3 |
|
|
| 4 |
|
<pre> |
| 5 |
|
|
| 6 |
joko@netfrag.org - sample stack: |
joko@netfrag.org - sample stack: |
| 7 |
|
|
| 8 |
o [task by joko] introduced "dispatchmail" to add mail2news-functionality to "recieveMail" (collector@netfrag.org) |
o [task by joko] introduced "dispatchmail" to add mail2news-functionality to "recieveMail" (collector@netfrag.org) |
| 65 |
|
|
| 66 |
o check out from cvs-repository: |
o check out from cvs-repository: |
| 67 |
o joko/doc -> /home/joko/public_html/computing/overview/topics/ |
o joko/doc -> /home/joko/public_html/computing/overview/topics/ |
| 68 |
o leaded to (A): |
o leaded to (A, B and C): see <a href="../topics/home2web.html">home2web</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: * 1 * * * ~/.cronrc-hourly |
|
|
o post message "About" (this) to announce@news.netfrag.org |
|
|
|
|
|
|
|
|
adduser: collector/col§$ |
|
|
|
|
|
|
|
|
some sample items occoured 2003-01-17 until 2003-01-26. |
|
|
|
|
|
what to do with that? |
|
|
o have all items stored in other applications conveniently. |
|
|
o be able to have items or references to them *archived* centrally |
|
|
o be able to access informations via *one* interface. |
|
|
actually *multiple* interfaces should be possible |
|
|
- the aim here is to get everything together (INTEGRATE!) (mnoGoSearch first! Torus::Archive later?) |
|
| 69 |
|
|
| 70 |
sysadmin tasks: |
o added user@netfrag.org: |
| 71 |
|
x adduser: collector/col§$ |
|
joko's tasks: |
|
| 72 |
|
|
| 73 |
|
o about: some sample items occoured 2003-01-17 until 2003-01-26. |
| 74 |
|
what to do with that? |
| 75 |
|
o have all items stored in other applications conveniently. |
| 76 |
|
o be able to have items or references to them *archived* centrally |
| 77 |
|
o be able to access informations via *one* interface. |
| 78 |
|
actually *multiple* interfaces should be possible |
| 79 |
|
- the aim here is to get everything together (INTEGRATE!) (mnoGoSearch first! Torus::Archive later?) |
| 80 |
|
|
| 81 |
|
o refactor topics: |
| 82 |
|
o make global-accessible@netfrag.org |
| 83 |
|
o introduce subtopics |
| 84 |
|
o sysadmin tasks |
| 85 |
|
o janosch's, jonen's and joko's tasks |
| 86 |
|
|
| 87 |
o start project "admintools" @ nfo/perl/scripts - including |
o start project "admintools" @ nfo/perl/scripts - including |
| 88 |
o getip.pl |
o getip.pl |
| 124 |
|
|
| 125 |
o rename "thread" to "newsgroup" in all scripts! |
o rename "thread" to "newsgroup" in all scripts! |
| 126 |
|
|
| 127 |
|
o what about: |
| 128 |
|
Torus::Xyz - solution to reuse concepts of Apache 2 and Cyrus 2!!! (and OpenLDAP???) for building an open collaboration server? |
| 129 |
|
|
| 130 |
|
o word-search: "identify" and "search" for |
| 131 |
|
|
| 132 |
|
o establish global "logs/" - like at http://moose.qx.net/logs/ |
| 133 |
|
|
| 134 |
|
o add redirecting page when someone wants to access |
| 135 |
|
o http://netfrag.org/~joko/phpChoPro/ or |
| 136 |
|
o http://netfrag.org/~joko/w2hfax/ |
| 137 |
|
|
| 138 |
|
o update mail-dispatching-rules |
| 139 |
|
o look at ilo.de/Inbox |
| 140 |
|
o move: logs/cvs/quepasa.netfrag.org -> logs/netfrag.org |
| 141 |
|
o look at netfrag.org/Inbox |
| 142 |
|
o if subject eq "Cron <joko@quepasa> ~/.cronrc-hourly" set target "logs/netfrag.org/joko/cron" [push over cron] |
| 143 |
|
o if subject matches "quepasa daily usenet report" at begin set target "logs/netfrag.org/news" [push over inn] |
| 144 |
|
o if subject matches "[CVS" at begin set target "logs/netfrag.org/cvs" [push over CVSSpam] |
| 145 |
|
o if mail is from myself set target "netfrag.org/Info" |
| 146 |
|
o write parser and engine to handle above declaration: Mail::Audit::Dispatch::Interface::Script |
| 147 |
|
|
| 148 |
|
o release mail from above from joko - introduce another email-address |
| 149 |
|
- e.g. work@netfrag.org, event@netfrag.org or tracker@netfrag.org (like collector@netfrag.org) |
| 150 |
|
|
| 151 |
|
|
| 152 |
|
</pre> |
| 153 |
|
|
| 154 |
|
</body> |
| 155 |
|
</html> |
Parent Directory
| 
Revision Log
| 
Patch
