Skip to content

Allow custom OCR model registry entries without forking #50

Description

@davanstrien

MODEL_REGISTRY now covers the built-in model set, but adding a private/custom OCR script still requires editing run.py.

Add a supported configuration path (for example YAML/TOML or repeatable CLI flags) that can define at least:

  • model slug and model id
  • uv-script URL
  • default hardware flavor and arguments
  • optional container image / Python / environment settings
  • display parameter count

Validation should fail before launching Jobs, and built-in registry entries should remain the zero-config default.

Split from #1 after the built-in model expansion was completed.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions