Skip to content

Release groups

The groups config lets you register your own release group name(s) so upPollo automatically flags matching uploads as personal releases and, optionally, as internal releases on a designated home tracker — without passing --personal-release or --internal on every upload. Each group can also carry its own signature that replaces upload_signature in the description.

A release name ends with a group tag (the part after the last -), for example MyGroup in Some.Movie.2024.1080p.WEB-DL.H264-MyGroup. When that tag matches one of your configured groups (case-insensitively), upPollo applies the appropriate flags per tracker.

Configuration

groups:
    - name: "MyGroup"        # personal release wherever supported
    - name: "4Rocket"
      internal_on: "rhd"     # home tracker: uploaded to rhd first AND marked internal there
      signature: "[b]4Rocket[/b]" # used instead of upload_signature
Field Required Description
name yes Your release group tag, matched case-insensitively against each release's group tag
internal_on no The group's home tracker (rhd). Matching releases are uploaded there first and flagged internal. Omit for personal-release-only
signature no BBCode signature for matching releases, used instead of upload_signature. Omit to keep upload_signature

Leave the list as groups: [] to disable the feature.

How it works

Personal release

For every target tracker that supports the personal-release flag, a matching release is flagged as a personal release. Both RocketHD and AnimeWorld support it.

Internal and the home tracker

Setting internal_on designates that tracker as the group's home. For a matching release:

  1. Upload order — the home tracker moves to the front of the target list and is uploaded to first (relevant with --tracker rhd,aw).
  2. Internal flag — the release is flagged internal on the home tracker.

Two conditions gate the internal flag:

  • Tracker support — only RocketHD currently supports internal uploads. AnimeWorld has no internal flag, so internal_on: "aw" is rejected during config validation.
  • Account permission — on RocketHD, the internal flag is applied only if your account may set it. RocketHD grants that to roles with moderator rights and to members of an internal release group, whatever their user group; upPollo asks the tracker before the upload. Without the permission the upload still proceeds — just without the internal flag — and a warning is printed. The home tracker is still uploaded to first.

Signature

Every upload description ends with your signature. By default that is the global upload_signature. When the release matches a group that has signature set, upPollo uses the group's signature instead; the global one is not added on top. Groups without signature keep using upload_signature.

The signature goes into the description of every tracker the release is uploaded to. Multi-line signatures work with a YAML block scalar:

groups:
    - name: "4Rocket"
      signature: |
          [b]4Rocket[/b]
          [img]https://example.com/4rocket-banner.png[/img]

Manual overrides

The CLI flags remain available as one-off overrides, subject to the same capability/permission gating:

  • -p, --personal-release — force a personal release for this upload.
  • -i, --internal — force an internal release for this upload (ignored, with a warning, if the tracker doesn't support it or your account isn't permitted).

Examples

Every release named ...-MyGroup flagged as a personal release on RocketHD and AnimeWorld:

groups:
    - name: "MyGroup"

Uploading ...-4Rocket with --tracker rhd,aw uploads to RocketHD first (flagged internal and personal release, if your role permits internal), then to AnimeWorld (flagged personal release):

groups:
    - name: "4Rocket"
      internal_on: "rhd"

Releases from MyGroup get the group banner as signature, every other release keeps the global one:

upload_signature: "[b]Uploaded by me[/b]"
groups:
    - name: "MyGroup"
      signature: "[img]https://example.com/mygroup-banner.png[/img]"

Validation

The config is validated on load. You get an error if a group name is empty, two groups share a name (case-insensitively), internal_on names an unknown tracker, or internal_on names a tracker without internal support (e.g. aw).