Deploy OVRTX Rendering API Standalone

Bring up just the OVRTX rendering API without the rest of an agent service stack. Useful when:

• Multiple agent CLIs (or services) need to share a single rendering host.
• The rendering GPU box is separate from the machine running the CLI / agent service.
• You want to iterate on the agent pipeline without rebooting the rendering container each time.

apps/ovrtx_rendering_api/ ships the Dockerfile, service code, and standalone docker-compose.yml. Use that compose file for shared render-service deployments so the command is not semantically tied to material or physics.

When to Use

• Use when the user wants a standalone OVRTX rendering API without a Material or Physics service stack.
• Use when multiple agent CLIs or services should share one rendering endpoint.
• Use when the render GPU host is separate from the machine running the agent CLI or service.
• Use service-specific Docker deploy skills when the user wants the bundled sidecar managed with that service stack.