|
|
| (5 intermediate revisions by 5 users not shown) |
| Line 2: |
Line 2: |
| {{shortcut|ISOP:ZODBOT}} | | {{shortcut|ISOP:ZODBOT}} |
|
| |
|
| zodbot is a supybot based irc bot that we use in our #fedora channels.
| |
|
| |
|
| == Contact Information ==
| | This SOP has moved to the fedora Infrastructure SOP git repo. Please see the current document at: https://docs.pagure.org/infra-docs/sysadmin-guide/sops/zodbot.html |
| Owner: Fedora Infrastructure Team
| |
|
| |
|
| Contact: #fedora-admin
| | For changes, questions or comments, please contact anyone in the Fedora Infrastructure team. |
| | |
| Location: Phoenix
| |
| | |
| Servers: noc1
| |
| | |
| Purpose: Provides our IRC bot
| |
| | |
| == Description ==
| |
| | |
| [[zodbot]] is a supybot based irc bot that we use in our #fedora channels. It runs on noc1 as the daemon user. We do not config manage the zodbot.conf because supybot makes changes to it on its own. Therefore it gets backed up and is treated as data.
| |
| | |
| == shutdown ==
| |
| | |
| <pre> killall supybot </pre>
| |
| | |
| == startup ==
| |
| | |
| <pre>
| |
| cd /srv/web/meetbot # zodbot current needs to be started in the meetbot directory.
| |
| # This requirement will go away in a later meetbot release.
| |
| sudo -u daemon supybot -d /var/lib/zodbot/conf/zodbot.conf</pre>
| |
| | |
| == Processing interrupted meeting logs ==
| |
| | |
| zodbot forgets about meetings if they are in progress when the bot goes down; therefore, the meetings never get processed. Users may request a ticket in [https://fedorahosted.org/fedora-infrastructure our Trac instance] to have meeting logs processed.
| |
| | |
| Trac tickets for meeting log processing should consist of a URL where zodbot had saved the log so far and an uploaded file containing the rest of the log. The logs are stored in /srv/www/meetbot. Append the remainder of the log uploaded to Trac (don't worry too much about formatting; meeting.py works well with irssi- and XChat-like logs), then run:
| |
| sudo python /usr/lib/python2.4/site-packages/supybot/plugins/MeetBot/meeting.py replay /path/to/fixed.log.txt
| |
| Close the Trac ticket, letting the user know that the logs are processed in the same directory as the URL they gave you.
| |
| | |
| == Becoming an admin ==
| |
| | |
| Register with zodbot on IRC.
| |
| | |
| /msg zodbot misc help register
| |
| | |
| You have to identify to the bot to do any admin type commands, and you need to have done so before anyone can give you privs.
| |
| | |
| After doing this, ping nirik on IRC and he will grant you privs if you need them. You'll likely be added to the admin group, which has the following capabilities (the below snippet is from an IRC log illustrating how to get the list of capabilities).
| |
| | |
| 21:57 < nirik> .list admin
| |
| 21:57 < zodbot> nirik: capability add, capability remove, channels, ignore add,
| |
| ignore list, ignore remove, join, nick, and part
| |
|
| |
|
|
| |
|
| [[Category:Infrastructure SOPs]] | | [[Category:Infrastructure SOPs]] |
