Administering Keen

Forgejo

Chapter 14 of 30

Forgejo

Forgejo collection records repository activity for chosen users or organisations, or the entries of a repository feed.

Enable and authenticate

Set KEEN_FORGEJO_ENABLED=true, KEEN_FORGEJO_BASE_URL and FORGEJO_TOKEN. The default FORGEJO_AUTH_MODE is token; feed authentication can also use FORGEJO_USERNAME or FORGEJO_COOKIE where the selected mode requires it.

Select users, organisations or feeds

Define a Forgejo source with its URL and credentials in Sources & evidence mapping.
Choose Add input on that source: User with the account login, Organisation with the organisation login, or Feed with a specific repository feed URL. Configure at least one before running the ingester.
Run a collection and inspect an actual event before choosing field paths. Repository activity is stored under activity; feed records can use rss.

Going deeper: discovery, lookback and shortcuts

User discovery covers repositories owned by that user; discovery repeats on each run and uses the token's visibility. Initial API activity collection looks back 14 days, subject to the upstream history available, and later runs use saved cursors. In a mapping rule, All collected events (any collection) selects events across the configured Forgejo collections, and the mapping editor's Set up collections shortcut opens collection setup for the selected source. Each named connection supplies its own endpoint and credentials; add repository or feed inputs to the appropriate connection.

Inspect and map evidence

Inspect a collected event and use Create mapping from this event. Structured selectors expose the payload that this source actually returns; a useful starting path is activity. Action and outcome filters use Keen's normalised event values. Preview matching and non-matching examples.

For file-managed deployments, collection inputs live in config/forgejo.yml. See the common collection workflow for UI configuration and override behaviour.