Why do you want to contribute?

I'm interested in contributing to Trigger.dev by fixing self‑hosted deployment bugs that affect users running the platform on their own infrastructure. Trigger.dev supports self‑hosting by letting users run the core services (webapp, worker, registry, etc.) in their own environment, but a few issues currently lead to runtime failures or degraded behavior for those setups.

I’ve been reviewing the relevant open issues and noticed a couple of problems with the self‑hosted Docker provider and managed indexer:

• #3257 — Local registry deployments can succeed without pushing the image, leading to a “No such image” error at runtime.
• #3259 — The managed indexer treats environment variable lookup failures as fatal instead of degrading gracefully.

Both of these issues impact the reliability of self‑hosted deployments — a key use case for teams that rely on full control of their infrastructure rather than the managed cloud offering. I’ve already set up the local development environment (Docker + pnpm) and have started exploring the code in apps/webapp/ and apps/supervisor/. Once vouched, I plan to open a draft PR addressing the image push validation logic in the Docker provider and follow up with fixes for the managed indexer.

Prior contributions or relevant experience

Here are some OSS projects that demonstrate my experience with backend APIs, async logic, and service complexity:

• https://github.com/flow-pie/chamaa.api — Backend API with async operations and business logic.
• https://github.com/flow-pie/OnlineVotingSystem.api — Full API project with auth, voting workflows, and consistency concerns.
• https://github.com/flow-pie/tyrant — OSS project focused on automation/processing patterns.

I’m comfortable with TypeScript, API design, async processing patterns, and building robust test suites. I’ve read the Trigger.dev contributing docs and understand the expectations for PRs, issues, and working with maintainers.