Changeset 1197 for obs_notify_generic


Ignore:
Timestamp:
10/13/15 12:33:31 (6 years ago)
Author:
joergs
Message:

fixes comments

File:
1 edited

Legend:

Unmodified
Added
Removed
  • obs_notify_generic/README.md

    r1186 r1197  
    3131-------------
    3232
    33 All configuration is done in the file
     33All configuration for this plugin is done in the file
    3434
    3535```
     
    4545but can be configured.
    4646
    47 The best configuration to start is by
     47The starting configuration could look like this:
    4848
    4949```
     
    5353```
    5454
    55 This logs all UNKNOWN events. With this configuration this are all events, as no specific events are defined.
     55This logs all UNKNOWN events. With this configuration this are all events, as no specific notification types are defined.
    5656
    5757Usefull notification types are
     
    6262Each event come with a number of parameter. These will also be logged.
    6363
    64 The configuration directove `filter` limits a notification type to certain cases. Filter can be regexes.
     64The configuration directive `filter` limits a notification type to certain cases. Filter can be regexes.
    6565
    6666Example:
     
    7575        },
    7676        {
    77             "filter" => { 'project' => '.*:bareos', 'repository' => 'SLE_12' },
     77            "filter" => { 'project' => '.*:bareos', 'repo' => 'SLE_12' },
    7878            "action" => 'logger "project $project published for repository $repository',
    7979            "log"    => 0,
     
    8484```
    8585
    86 Meaing:
     86Meaning:
    8787  * type=REPO_PUBLISH_STATE
    8888    * ignore it
     
    9292
    9393Limitations:
    94   * the `action` run as user obsrun. As the OBS service run as daemon, only very few environment variables are set.
    95   * the `action`s should have a short runtime. As long as these scripts run, some other services from the obs are blocked. Maybe the scripts are forcefully ended by the OBS service.
     94  * the `action` run as user obsrun. As the OBS service run as daemon, only very few environment variables are set. It might help to call scripts using `sudo -u USERNAME`
     95  * the `action` script do run in background, to prevent blocking other OBS services. Output will be write to `${logfile}.out.log`.
Note: See TracChangeset for help on using the changeset viewer.