feat: Add OmniRoute - Free LLM Gateway Template

[df4p]

Adding the OmniRoute template to Dokploy.

Never stop coding. Free AI gateway: one endpoint, 160+ providers (50+ free), connect Claude Code, Codex, Cursor, Cline & Copilot to FREE Claude/GPT/Gemini. RTK+Caveman stacked compression saves 15-95% tokens, smart auto-fallback, MCP/A2A, multimodal APIs, Desktop/PWA.

What is this PR about?

New PR of [Template Name]

Checklist

Before submitting this PR, please make sure that:

• I have read the suggestions in the README.md file https://github.com/Dokploy/templates?tab=readme-ov-file#general-requirements-when-creating-a-template
• I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
• I have added tests that demonstrate that my correction works or that my new feature works.

Issues related (if applicable)

Close automatically the related issues using the keywords: closes #ISSUE_NUMBER

Screenshots or Videos

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
templates	✅ Ready (View Log)	Visit Preview	a242210

[df4p]

My first PR. Did read all the docs and tried to follow all the patterns of the meta.json, .toml & compose.

Do I have to try once again to PR?

[nerkoux]

Hey @df4p . I noticed a couple of issues that are currently causing the validation workflow to fail:

1. pnpm-workspace.yaml

This file appears to have been added as part of the PR:

allowBuilds:
  esbuild: false

The templates repository does not require this file for blueprint contributions, and its current contents result in:

ERR_PNPM_INVALID_WORKSPACE_CONFIGURATION packages field missing or empty

Remove the app/pnpm-workspace.yaml from the PR unless it is required by a separate repository-wide change.

2. Invalid TOML syntax

The validation error originates from blueprints/omniroute/template.toml.

The following entry is not valid TOML:

STORAGE_ENCRYPTION_KEY_VERSION=v1

String values must be quoted:

STORAGE_ENCRYPTION_KEY_VERSION = "v1"

It would also be good to review other string values in [config.env] and ensure they are properly quoted for TOML compatibility.

After removing the workspace file and fixing the TOML syntax, the validation workflow should proceed further.

[df4p]

I've made the changes and don't know what else I must do to make the PR go with it.

[df4p]

Looks like it passed on all checks now. Just waiting.

[nerkoux]

@df4p that's good!