Changes between Version 5 and Version 6 of JabberTracScript
- Timestamp:
- Nov 25, 2015, 9:03:52 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
JabberTracScript
v5 v6 17 17 == Download 18 18 19 Download the zipped source from [ download:jabbertracscript here].19 Download the zipped source from [export:jabbertracscript here]. 20 20 21 21 == Source 22 22 23 You can check out JabberTracScript from [ http://trac-hacks.org/svn/jabbertracscript here] using Subversion, or [source:jabbertracscript browse the source] with Trac.23 You can check out JabberTracScript from [/svn/jabbertracscript here] using Subversion, or [source:jabbertracscript browse the source] with Trac. 24 24 25 == Configuration25 == Installation and Configuration 26 26 27 First you'll need to have a working Trac environment. 28 Then, install and enable plugin TicketBackLinksMacro. 27 On a working Trac environment install and enable the TicketBackLinksMacro. 29 28 Then you will need a Jabber server with logging enabled, for chatrooms, configured to be ordered by subdirectories (dates). Jabber with jcr and muc is known to work ok. 30 29 … … 35 34 You can make a cron to launch j2t (without arguments) each time you want it to be updated. 36 35 37 WARNING: This should be done at most once a day, otherwise it will make too much noise on your timelines.36 '''Warning''': This should be done at most once a day, otherwise it will make too much noise on your timelines. 38 37 39 38 === Recommendations … … 41 40 Now, you'll have logs uploaded to wiki and shown in tickets' description. I recommend using TracFineGrainedPermissions to block undesired traffic to the conversations. 42 41 43 Chatrooms will not be created automatically, so, if they don't exists, you 'll have to join to them. A workaround for automatising this is having a gozerbot doing that workfor you.42 Chatrooms will not be created automatically, so, if they don't exists, you will have to join to them. A workaround for automating this is having a gozerbot doing that for you. 44 43 45 I've also built a gozerplug for this: j2t.py. 46 You'll have to modify it a bit, since it's ready to get config trought ssh, and that might not be what you want. Also, you'll have to configure that user 47 to don't require passwords if you use ssh, because of certificates. 44 I've also built a gozerplug for this: `j2t.py`. 45 You'll have to modify it a bit, since it's ready to get config trough ssh, and that might not be what you want. Also, you'll have to configure that user to don't require passwords if you use ssh, because of certificates. 48 46 49 47 If you wan't you can configure your bot nick inside j2t (botnick variable) so its messages won't be shown. Also, commands are not saved (!whatever strings) into wiki.