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?) |
|
|
|
|
|
sysadmin tasks: |
|
69 |
|
|
70 |
joko's tasks: |
o added user@netfrag.org: |
71 |
|
x adduser: collector/col§$ |
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 marked message to Spam? Newsletters? |
141 |
|
o move: logs/cvs/quepasa.netfrag.org -> logs/netfrag.org |
142 |
|
o look at netfrag.org/Inbox |
143 |
|
o if subject eq "Cron <joko@quepasa> ~/.cronrc-hourly" set target "logs/netfrag.org/joko/cron" [push over cron] |
144 |
|
o if subject matches "quepasa daily usenet report" at begin set target "logs/netfrag.org/news" [push over inn] |
145 |
|
o if subject matches "[CVS" at begin set target "logs/netfrag.org/cvs" [push over CVSSpam] |
146 |
|
o if mail is from myself set target "netfrag.org/Info" |
147 |
|
o look at quepasa.netfrag.org/Inbox |
148 |
|
o [Multisync-users] |
149 |
|
o [Kroupware] |
150 |
|
|
151 |
|
o write parser and engine to handle above declaration: Mail::Audit::Dispatch::Interface::Script |
152 |
|
|
153 |
|
|
154 |
|
o release mail from above from joko - introduce another email-address |
155 |
|
- e.g. work@netfrag.org, event@netfrag.org or tracker@netfrag.org (like collector@netfrag.org) |
156 |
|
|
157 |
|
o Multisync & SyncML |
158 |
|
o post something to mailing-list...!? |
159 |
|
|
160 |
|
o the '.cvslink'-mechanism: |
161 |
|
o type: ln -s /home/joko/public_html/_web/_cvs.php . |
162 |
|
|
163 |
|
o LinkContainer |
164 |
|
- insert via drag & drop |
165 |
|
- shows links hierarchically |
166 |
|
|
167 |
|
o (Self)Info - mails to yourself |
168 |
|
o convert all "(Self)Info" mails to |
169 |
|
news-messages - use "formail" and ...? |
170 |
|
|
171 |
|
o h1.service.netfrag.org |
172 |
|
o base os-upgrade: suse X -> debian 3.0 |
173 |
|
|
174 |
|
o dispatchmail |
175 |
|
o are Mail-Headers already added? |
176 |
|
|
177 |
|
o workflow (PostThisLink) |
178 |
|
o drag link from done google-search ... |
179 |
|
o ... to container (at the current Task) |
180 |
|
o a news-post is created automagically |
181 |
|
o use this: |
182 |
|
[smtp-header-fields] |
183 |
|
From: expanded email-address resolved from Name|Nickname in Addressbook (via LDAP!) |
184 |
|
Subject: googled for "<search-request>" |
185 |
|
[body] |
186 |
|
o include into mime-part if not already included |
187 |
|
o fetch from web on demand |
188 |
|
|
189 |
|
o ssl/tls for inn? |
190 |
|
|
191 |
|
o dispatchmail |
192 |
|
o re-link as sub-/module-project under Torus::Content::Gateway |
193 |
|
o -> Torus::Content - a content delivery engine |
194 |
|
o -> additional idea: Torus::Content::Gateway is "just" the API to "Torus::Item::Router" in this case |
195 |
|
o 'Torus::Content::Gateway' would then route 'Torus::Item::RFC822'-objects using 'Torus::Item::Router' |
196 |
|
o look at sieve - jonen posted to nfo.links.computing: [r:Message-ID: <b0ppj7$7gv$1@quepasa.netfrag.org>] |
197 |
|
|
198 |
|
o finally: do actually establish 'Torus' at 'nfo/perl/libs' |
199 |
|
|
200 |
|
o pod: checkout how to make references which expand to html-urls |
201 |
|
o does pod handle this or do we need external link-expansion for this task? |
202 |
|
o how to make references to news-messages? |
203 |
|
e.g.: |
204 |
|
o Message-ID: <b0ppj7$7gv$1@quepasa.netfrag.org> |
205 |
|
o news://news.netfrag.org/nfo.links.computing |
206 |
|
o proposal(s): |
207 |
|
o http://news.netfrag.org/id=b0ppj7$7gv$1@quepasa.netfrag.org |
208 |
|
o http://news.netfrag.org/nfo.links.computing/subject=FilteringMailWithSieve of wiki |
209 |
|
o http://news.netfrag.org/nfo.links.computing/id=b0ppj7$7gv$1@quepasa.netfrag.org |
210 |
|
|
211 |
|
o what about the '.nws'-files on ms? (for news-messages) |
212 |
|
|
213 |
|
o display-mode: everything strictly hierarchical to get maximum overview!!! |
214 |
|
|
215 |
|
</pre> |
216 |
|
|
217 |
|
</body> |
218 |
|
</html> |