| 1 |
joko |
1.1 |
joko@netfrag.org - sample stack: |
| 2 |
|
|
|
| 3 |
|
|
o [task by joko] introduced "dispatchmail" to add mail2news-functionality to "recieveMail" (collector@netfrag.org) |
| 4 |
|
|
x [task by joko] migrated joko_mail from "receiveMail" to "dispatchmail" |
| 5 |
|
|
x [bug from joko] what about mailing from the cli / mails sent from the system (e.g. via CVSSpam): |
| 6 |
|
|
mail is sent out coming from <username>@quepasa.netfrag.org |
| 7 |
|
|
--> how to configure just having <username>@netfrag.org right here??? |
| 8 |
|
|
x [resolved by jonen] CVSSpam: janosch@netfrag.org: |
| 9 |
|
|
x cd /etc/mail |
| 10 |
|
|
x nano sendmail.mc |
| 11 |
|
|
x add/replace line: MASQUERADE_AS(`netfrag.org') |
| 12 |
|
|
x make |
| 13 |
|
|
x /etc/init.d/sendmail reload |
| 14 |
|
|
o [bug from joko] "su root" is needed sometimes |
| 15 |
|
|
else PATH is not set correctly |
| 16 |
|
|
and maybe something other |
| 17 |
|
|
compiling fails always |
| 18 |
|
|
x [task by joko] these items already have been refactored into other Tasks, Notes and/or Bug Requests - this Note is just FYI. |
| 19 |
|
|
o [task by joko] dispatchmail - project work |
| 20 |
|
|
x README.pod -> README.html |
| 21 |
|
|
x link with "topics.html" properly |
| 22 |
|
|
x write something about data-/control-flow to README.pod |
| 23 |
|
|
|
| 24 |
|
|
o look (in detail) at Cyrus Netnews |
| 25 |
|
|
[...] |
| 26 |
|
|
The IMAP server can export netnews newsgroups as IMAP mailboxes. |
| 27 |
|
|
[...] |
| 28 |
|
|
o collectnews, rmnews, syncnews |
| 29 |
|
|
x seems to make an external web-based newsreader unneccessary!!! |
| 30 |
|
|
|
| 31 |
|
|
o tie together mail, news and html |
| 32 |
|
|
o write mini-howto |
| 33 |
|
|
|
| 34 |
|
|
o link with erfrakon |
| 35 |
|
|
|
| 36 |
|
|
o sieve? |
| 37 |
|
|
|
| 38 |
|
|
o post some old mails to news.netfrag.org! |
| 39 |
|
|
|
| 40 |
|
|
o what about "dev@netfrag.org"? |
| 41 |
|
|
|
| 42 |
|
|
o nfo/perl/libs |
| 43 |
|
|
x ts |
| 44 |
|
|
x outlook2ldap |
| 45 |
|
|
x dispatchmail |
| 46 |
|
|
o get the essence (project- and development work - the whole workflow) out of it! write it down! in detail! |
| 47 |
|
|
|
| 48 |
|
|
o netfrag.org-workflow: |
| 49 |
|
|
o technical questions to support@netfrag.org? |
| 50 |
|
|
o publish them via news! |
| 51 |
|
|
o queue them into / integrate with TUTOS somehow!!! |
| 52 |
|
|
|
| 53 |
|
|
o new threads@news.netfrag.org: |
| 54 |
|
|
x ctlinnd newgroup nfo.support.queue |
| 55 |
|
|
x ctlinnd newgroup nfo.support.faq |
| 56 |
|
|
|
| 57 |
|
|
x new account for janosch@news.netfrag.org |
| 58 |
|
|
x nano /etc/news/nnrp.access |
| 59 |
|
|
x added line: *:Read Post:janosch:janosch:* |
| 60 |
|
|
|
| 61 |
|
|
o check out from cvs-repository: |
| 62 |
|
|
o joko/doc -> /home/joko/public_html/computing/overview/topics/ |
| 63 |
|
|
o leaded to (A): |
| 64 |
|
|
o write mini-howto: "howto use, document and enhance the '.cvslink'-symlinking-mechanism" |
| 65 |
|
|
o introduce command to 'tiki-workflow|tiki-publish' |
| 66 |
|
|
x introduced '.cvs'-interface (directory-style) |
| 67 |
|
|
x now directly accessible (but hidden) via http://netfrag.org/~joko/computing/overview/topics/.cvs/ |
| 68 |
|
|
x here: made public by adding a "README.html" (or "HEADER.html") which either: |
| 69 |
|
|
x includes a html-link (a-tag) to './.cvs' |
| 70 |
|
|
o makes a redirect via meta-tags or javascript |
| 71 |
|
|
o leads to (B): |
| 72 |
|
|
o start 'home2web': |
| 73 |
|
|
x begin with having an overview of the recent topics stored in cvs |
| 74 |
|
|
x continue by expanding this topic-list through more details |
| 75 |
|
|
x use mechanisms delivered from Apache |
| 76 |
|
|
x HEADER.html, README.html |
| 77 |
|
|
x php: http-redirect |
| 78 |
|
|
o add more links! |
| 79 |
|
|
o fix proposals of how links should be expanded (maybe post RFC to news.netfrag.org first? -> create newsgroup 'nfo.rfc') |
| 80 |
|
|
x manually? no! (hmmm, grrrr......) |
| 81 |
|
|
o pod? for now! |
| 82 |
|
|
o DocBook? not yet! |
| 83 |
|
|
o some wiki? why not? |
| 84 |
|
|
o add links to internal tools (e.g. TUTOS, chora, etc.) |
| 85 |
|
|
o add external links |
| 86 |
|
|
o add co-worker topics |
| 87 |
|
|
o leads to (C): |
| 88 |
|
|
o write mini-howto: web publishing with cvs |
| 89 |
|
|
- write in pod |
| 90 |
|
|
- commit to cvs |
| 91 |
|
|
- checkout from cvs |
| 92 |
|
|
- build html from pod |
| 93 |
|
|
- publish html |
| 94 |
|
|
x do that regularly / in interval: use cron! |
| 95 |
|
|
su joko |
| 96 |
|
|
cd ~ |
| 97 |
|
|
nano .cronrc-hourly |
| 98 |
|
|
add line(s): [...] cvs update topics [...] |
| 99 |
|
|
crontab -e |
| 100 |
|
|
add line: * 1 * * * ~/.cronrc-hourly |
| 101 |
|
|
o post message "About" (this) to announce@news.netfrag.org |
| 102 |
|
|
|
| 103 |
|
|
|
| 104 |
|
|
adduser: collector/col§$ |
| 105 |
|
|
|
| 106 |
|
|
|
| 107 |
|
|
some sample items occoured 2003-01-17 until 2003-01-26. |
| 108 |
|
|
|
| 109 |
|
|
what to do with that? |
| 110 |
|
|
o have all items stored in other applications conveniently. |
| 111 |
|
|
o be able to have items or references to them *archived* centrally |
| 112 |
|
|
o be able to access informations via *one* interface. |
| 113 |
|
|
actually *multiple* interfaces should be possible |
| 114 |
|
|
- the aim here is to get everything together (INTEGRATE!) (mnoGoSearch first! Torus::Archive later?) |
| 115 |
|
|
|
| 116 |
|
|
sysadmin tasks: |
| 117 |
|
|
|
| 118 |
|
|
joko's tasks: |
| 119 |
|
|
|
| 120 |
|
|
|
| 121 |
|
|
o start project "admintools" @ nfo/perl/scripts - including |
| 122 |
|
|
o getip.pl |
| 123 |
|
|
o notify.pl |
| 124 |
|
|
x on uml-event: up/down/reboot |
| 125 |
|
|
o on news-post (dispatchmail: mail2news) |
| 126 |
|
|
o on cvs-checkout (done on interval with joko/doc - see above) |
| 127 |
|
|
o on build (build.pl) |
| 128 |
|
|
o some tools from dispatchmail |
| 129 |
|
|
o dispatchmail itself! |
| 130 |
|
|
o |
| 131 |
|
|
|
| 132 |
|
|
o [idea] ;-) for symbols (in general) |
| 133 |
|
|
- o = Open Task |
| 134 |
|
|
- x = Closed Task |
| 135 |
|
|
(- [<TopicName>] = name of topic - fixed/proposed) |
| 136 |
|
|
- [<TopicType> by|for <UserName>] = |
| 137 |
|
|
- type of topic - fixed/proposed |
| 138 |
|
|
- username who submitted this item / should this item be assigned to |
| 139 |
|
|
- this could become a language for describing the workflow |
| 140 |
|
|
- this proposal should be the shortcut-form in wiki-style: (e.g. make 'tiki-workflow' from that?) |
| 141 |
|
|
- more verbose (e.g. XML) - forms could/should become possible (e.g. 'WFML') (WorkFlow Markup|Modeling Language) |
| 142 |
|
|
- TODO: refactor this document after further commits to show off refactoring process through cvs-revisioning! |
| 143 |
|
|
o required for this: link to a page which shows the history of a document not as verbose as (e.g.) chora does |
| 144 |
|
|
- d = from 'tbd': to-be-discussed |
| 145 |
|
|
- c = cancelled |
| 146 |
|
|
|
| 147 |
|
|
o [idea] ;-) for symbols (in _this_ document here) (parser|engine behaviour modification) |
| 148 |
|
|
- R = from 'tbr': to-be-refactored |
| 149 |
|
|
- r = already refactored elsewhere |
| 150 |
|
|
- an "r" may also mean "reference" ;-) |
| 151 |
|
|
- make 'r-http://netfrag.org/to/another/reference/wrapped/via/http/' possible in documentation |
| 152 |
|
|
- also the shortcut form: [r:/to/another/reference/wrapped/via/http/] |
| 153 |
|
|
- this - and only this - should be the minimalst requried definition of a "reference" |
| 154 |
|
|
- an internet "link" - however needs some more metadata around it: an "url" and a "caption" - what about these? |
| 155 |
|
|
- either fetch them from archive-metadata of this reference ... |
| 156 |
|
|
- ... or use the name directly as caption and build the url against a known redirector handler which |
| 157 |
|
|
accesses the archive-metadata |
| 158 |
|
|
|
| 159 |
|
|
o rename "thread" to "newsgroup" in all scripts! |
| 160 |
|
|
|
Parent Directory
| 
Revision Log
