[codex] fix: update firecrawl template for v2.8.0

[Manan-Santoki]

Summary

• align the Firecrawl Dokploy template with the current upstream self-hosted architecture
• pin Firecrawl source builds to v2.8.0 and switch startup to the upstream harness entrypoint
• update the template env model for PostgreSQL and RabbitMQ, and refresh the meta.json entry

What changed

• replaced the stale split-process Firecrawl deployment with the current harness-driven api service
• added the missing rabbitmq dependency and kept redis, playwright-service, and nuq-postgres
• changed Firecrawl-owned services from latest images to remote source builds pinned to v2.8.0
• updated Dokploy template variables to use POSTGRES_*, NUQ_RABBITMQ_URL, and current optional Firecrawl envs
• pinned the Firecrawl metadata version to v2.8.0
• running the required meta processing also removed a pre-existing duplicate strapi entry from meta.json

Root cause

The existing Firecrawl template still launched the old runtime layout using node --import ./dist/src/otel.js .... Upstream Firecrawl now starts through node dist/src/harness.js --start-docker and expects RabbitMQ plus harness-managed workers, so the old Dokploy template crashed with ERR_MODULE_NOT_FOUND for /app/dist/src/otel.js.

Impact

Dokploy users should get a Firecrawl deployment shape that matches current upstream self-hosting instead of the broken legacy image startup path. The template is also now version-pinned instead of following latest.

Validation

• node dedupe-and-sort-meta.js
• docker compose -f blueprints/firecrawl/docker-compose.yml config
• npm run validate-docker-compose -- --file ../blueprints/firecrawl/docker-compose.yml (from build-scripts/)
• npm run validate-template -- --dir ../blueprints/firecrawl (from build-scripts/)
• git diff --check

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

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