mount a generated /app/config.yml with documented production-oriented defaults
enable JWT auth, rate limiting, health/metrics observability, and stricter healthchecks
update the template metadata and docs link to match the current self-hosting docs
Why
The existing blueprint was still on latest/0.7.3 and only exposed basic provider env vars. It did not reflect Crawl4AI's current 0.8.0 self-hosting guidance around pinned versions, OpenAI-compatible base URLs, mounted config.yml, or built-in security and observability features.
Impact
Dokploy users can point Crawl4AI at OpenRouter by setting OPENAI_API_KEY to an OpenRouter key and using the default OPENAI_BASE_URL
the deployment now ships with JWT auth enabled by default instead of being exposed without app-layer auth
the template better matches the current Crawl4AI self-hosting docs and feature set
Validation
ran node dedupe-and-sort-meta.js
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/Dokploy/templates/pull/770
**Author:** [@Manan-Santoki](https://github.com/Manan-Santoki)
**Created:** 4/4/2026
**Status:** 🔄 Open
**Base:** `canary` ← **Head:** `codex/crawl4ai-openrouter-0-8-0`
---
### 📝 Commits (9)
- [`d9c507e`](https://github.com/Dokploy/templates/commit/d9c507e093b32d211a96f6688f1e5eb105b58921) fix: update firecrawl template for v2.8.0
- [`8112a1b`](https://github.com/Dokploy/templates/commit/8112a1b42d91f71d2eb1179ae9b0a1b59c3110f2) fix(firecrawl): use redis 7 alpine
- [`4cb06de`](https://github.com/Dokploy/templates/commit/4cb06dee9d04fe5f99d843a0f6a068a0358cb750) fix(firecrawl): default boolean env values
- [`3ae7042`](https://github.com/Dokploy/templates/commit/3ae70429e61876c478b2b5f23a54bd900e71d23b) fix(firecrawl): use postgres defaults for nuq init
- [`8033481`](https://github.com/Dokploy/templates/commit/80334813e6490a34f0f6051345d0ae8832cb352b) docs(firecrawl): document template env variables
- [`f93a44e`](https://github.com/Dokploy/templates/commit/f93a44e12c6d9ecb72bb8962e89344b3005d579a) fix(firecrawl): default optional env vars to empty
- [`d486003`](https://github.com/Dokploy/templates/commit/d486003df62167c496ea3553131d3953403f92e9) fix(firecrawl): wire supabase auth envs
- [`96a0803`](https://github.com/Dokploy/templates/commit/96a08037cae9f7bdf407b3c23beea40aebf28f76) feat: improve crawl4ai template
- [`8aa0076`](https://github.com/Dokploy/templates/commit/8aa0076f4b2902590fbebf10dc78f03dcd3028d2) fix: align crawl4ai config with 0.8.0
### 📊 Changes
**5 files changed** (+294 additions, -116 deletions)
<details>
<summary>View changed files</summary>
📝 `blueprints/crawl4ai/docker-compose.yml` (+10 -3)
📝 `blueprints/crawl4ai/template.toml` (+110 -2)
📝 `blueprints/firecrawl/docker-compose.yml` (+70 -59)
📝 `blueprints/firecrawl/template.toml` (+99 -29)
📝 `meta.json` (+5 -23)
</details>
### 📄 Description
## What changed
- pin the Crawl4AI image to `0.8.0`
- add OpenRouter-ready OpenAI-compatible env settings
- mount a generated `/app/config.yml` with documented production-oriented defaults
- enable JWT auth, rate limiting, health/metrics observability, and stricter healthchecks
- update the template metadata and docs link to match the current self-hosting docs
## Why
The existing blueprint was still on `latest`/`0.7.3` and only exposed basic provider env vars. It did not reflect Crawl4AI's current `0.8.0` self-hosting guidance around pinned versions, OpenAI-compatible base URLs, mounted `config.yml`, or built-in security and observability features.
## Impact
- Dokploy users can point Crawl4AI at OpenRouter by setting `OPENAI_API_KEY` to an OpenRouter key and using the default `OPENAI_BASE_URL`
- the deployment now ships with JWT auth enabled by default instead of being exposed without app-layer auth
- the template better matches the current Crawl4AI self-hosting docs and feature set
## Validation
- ran `node dedupe-and-sort-meta.js`
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/Dokploy/templates/pull/770
Author: @Manan-Santoki
Created: 4/4/2026
Status: 🔄 Open
Base:
canary← Head:codex/crawl4ai-openrouter-0-8-0📝 Commits (9)
d9c507efix: update firecrawl template for v2.8.08112a1bfix(firecrawl): use redis 7 alpine4cb06defix(firecrawl): default boolean env values3ae7042fix(firecrawl): use postgres defaults for nuq init8033481docs(firecrawl): document template env variablesf93a44efix(firecrawl): default optional env vars to emptyd486003fix(firecrawl): wire supabase auth envs96a0803feat: improve crawl4ai template8aa0076fix: align crawl4ai config with 0.8.0📊 Changes
5 files changed (+294 additions, -116 deletions)
View changed files
📝
blueprints/crawl4ai/docker-compose.yml(+10 -3)📝
blueprints/crawl4ai/template.toml(+110 -2)📝
blueprints/firecrawl/docker-compose.yml(+70 -59)📝
blueprints/firecrawl/template.toml(+99 -29)📝
meta.json(+5 -23)📄 Description
What changed
0.8.0/app/config.ymlwith documented production-oriented defaultsWhy
The existing blueprint was still on
latest/0.7.3and only exposed basic provider env vars. It did not reflect Crawl4AI's current0.8.0self-hosting guidance around pinned versions, OpenAI-compatible base URLs, mountedconfig.yml, or built-in security and observability features.Impact
OPENAI_API_KEYto an OpenRouter key and using the defaultOPENAI_BASE_URLValidation
node dedupe-and-sort-meta.js🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.