drupflare/worker - v1.0.4
    Preparing search index...

    Interface CronOptions

    every knob the GC passes and the chain accept; each reads only what it needs

    interface CronOptions {
        chainMs?: number;
        healthObservation?: Record<string, unknown>;
        hookPolicy?: Record<string, CronHookPolicy>;
        hooks?: string[];
        idleMs?: number;
        includeAdvisories?: boolean;
        includeCronLast?: boolean;
        includeFetchReopen?: boolean;
        includeHealth?: boolean;
        includeQueue?: boolean;
        maxQueueRepeats?: number;
        maxRows?: number;
        nowMs?: number;
        origin?: string;
        pass?: string;
        queueBatchSize?: number;
        rowLimit?: number;
        tables?: string[];
    }
    Index
    chainMs?: number
    healthObservation?: Record<string, unknown>

    What the host already knows about itself, handed to BootSelfTest.

    Every key is a host fact, so passing them in lets the unit run with no Drupal kernel.

    hookPolicy?: Record<string, CronHookPolicy>
    hooks?: string[]
    idleMs?: number
    includeAdvisories?: boolean

    the advisory scan unit; off only for a test that is measuring something else

    includeCronLast?: boolean
    includeFetchReopen?: boolean

    the update-fetch reopen unit; off only for a test that is measuring something else

    includeHealth?: boolean

    the PHP health unit; off only for a test that is measuring something else

    includeQueue?: boolean
    maxQueueRepeats?: number
    maxRows?: number
    nowMs?: number
    origin?: string

    The scheme://host[:port] a cron fragment boots Drupal against.

    Cron sends mail and user_pass_reset_url() builds an absolute link from the request, so the default would point every mailed link at the recipient's own machine. Empty keeps that default, which is right for a probe.

    pass?: string
    queueBatchSize?: number
    rowLimit?: number
    tables?: string[]