File: grok-pi-piper.1.rst

package info (click to toggle)
grokmirror 2.0.12-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 516 kB
  • sloc: python: 3,711; sh: 70; makefile: 8
file content (84 lines) | stat: -rw-r--r-- 2,389 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
GROK-PI-PIPER
=============
-----------------------------------------------------------
Hook script for piping new messages from public-inbox repos
-----------------------------------------------------------

:Author:    mricon@kernel.org
:Date:      2020-10-07
:Copyright: The Linux Foundation and contributors
:License:   GPLv3+
:Version:   2.0.2
:Manual section: 1

SYNOPSIS
--------
    grok-pi-piper [-h] [-v] [-d] -c CONFIG [-l PIPELAST] [--version] repo

DESCRIPTION
-----------
This is a ready-made hook script that can be called from
pull.post_update_hook when mirroring public-inbox repositories. It will
pipe all newly received messages to arbitrary commands defined in the
config file. The simplest configuration for lore.kernel.org is::

    ~/.config/pi-piper.conf
    -----------------------
    [DEFAULT]
    pipe = /usr/bin/procmail
    # Prune successfully processed messages
    shallow = yes

    ~/.procmailrc
    -------------
    DEFAULT=$HOME/Maildir/
    
    # Don't deliver cross-posted duplicates
    :0 Wh: .msgid.lock
    | formail -D 8192 .msgid.cache

    ~/.config/lore.conf
    -------------------
    [core]
    toplevel = ~/.local/share/grokmirror/lore
    log = ${toplevel}/grokmirror.log

    [remote]
    site = https://lore.kernel.org
    manifest = https://lore.kernel.org/manifest.js.gz

    [pull]
    post_update_hook = ~/.local/bin/grok-pi-piper -c ~/.config/pi-piper.conf
    include = /list-you-want/*
              /another-list/*

It assumes that grokmirror was installed from pip. If you installed it
via some other means, please check the path for the grok-pi-piper
script.

Note, that initial clone may take a long time, even if you set
shallow=yes.

See pi-piper.conf for other config options.


OPTIONS
-------
  -h, --help            show this help message and exit
  -v, --verbose         Be verbose and tell us what you are doing (default: False)
  -d, --dry-run         Do a dry-run and just show what would be done (default: False)
  -c CONFIG, --config CONFIG
                        Location of the configuration file (default: None)
  -l PIPELAST, --pipe-last PIPELAST
                        Force pipe last NN messages in the list, regardless of tracking (default: None)
  --version             show program's version number and exit


SEE ALSO
--------
* grok-pull(1)
* git(1)

SUPPORT
-------
Email tools@linux.kernel.org.