Archive:Hermes administration
|
This article is being considered for deletion! Reason: openSUSE is not using Hermes anymore, development has stopped in 2013.. Please do not blank, merge, or move this article, or remove this notice. Refer to this article's discussion page and our deletion policy for more information. |
This page gives some hints on how to administer Hermes.
If you need further assistance (and you probably will ;-) do not hesitate to ask in IRC on freenode in the boosters channel #opensuse-boosters.
Configuration File
Hermes needs a config file which is /etc/hermes.conf Make sure to edit it properly. See Hermes Hacking for more information about it.
Deliveries
Hermes provides several ways to deliver messages to the user. They are configured in the database in table deliveries. Changes to it have to be done via the mysql shell currently.
Hermes checks the name on which delivery sub routine to call. The following delivery types are recognised currently:
| Delivery Type | What it means |
|---|---|
| Send per electronic mail | |
| jabber | notifies through the jabber protocoll |
| RSS | creates a RSS feed |
| HTTP | lets Hermes call an url for you |
| calls the twitter API |
Note that one can administer more than one deliveries of each type, for example one called Twitter_openSUSE and another called Twitter_SLE. The important thing is that the string Twitter (case insensitive) appears in the name.
Delivery Attributes
In order to specify important additional information for each of the delivery types, there is the concept of delivery attributes which can be specified. The following attributes are considered for the delivery types:
| Delivery Type | Attribute | What it means |
|---|---|---|
| send_signed_mails | set it to make Hermes signing the mails before sending. Be aware of security issues and performance gaps. | |
| HTTP | url | specify the url of the url to call. The url string can contain Template variables. |
| access_token | the twitter API access token | |
| access_token_secret | the twitter API access secret | |
| user_id | the twitter API user id | |
| screen_name | the twitter API display name | |
| consumer_key | the twitter API consumer key | |
| consumer_secret | the twitter API consumer secret |
The attributes still have to be created manually in the database into table delivery_attributes.