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
Greptile Summary
This PR adds a new imgproxy template for fast and secure on-the-fly image processing. The implementation includes a two-service setup with imgproxy for image processing and nginx as a caching reverse proxy.
Key changes:
Added blueprints/imgproxy/ with docker-compose.yml, template.toml, and logo
Created properly configured environment variables with secure defaults (key/salt using ${hash:128})
Implemented nginx caching layer with configurable cache settings
Updated meta.json with correct metadata and proper alphabetical ordering
Used appropriate Docker image versions (imgproxy v3.30.1, nginx 1.28.2-alpine)
Issues found:
The nginx service uses ports instead of expose, which violates template requirements (AGENTS.md line 150)
The imgproxy service should explicitly declare expose: - 8080 for documentation
Confidence Score: 4/5
This PR is largely safe to merge with minor syntax corrections needed
The template follows most best practices with proper versioning, secure variable generation, and good architecture. However, it uses ports instead of expose in the nginx service, which violates documented template requirements. Once this syntax issue is corrected, the template will be production-ready.
Pay attention to blueprints/imgproxy/docker-compose.yml - needs ports changed to expose
🔄 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/714
**Author:** [@vladyslavprosolupov](https://github.com/vladyslavprosolupov)
**Created:** 2/19/2026
**Status:** ✅ Merged
**Merged:** 3/5/2026
**Merged by:** [@Siumauricio](https://github.com/Siumauricio)
**Base:** `canary` ← **Head:** `canary`
---
### 📝 Commits (8)
- [`0e58d08`](https://github.com/Dokploy/templates/commit/0e58d08bd1f08e0a26c7ef863a52b5a0796d0d8e) feat: Add imgproxy template
- [`5da44de`](https://github.com/Dokploy/templates/commit/5da44de7e5dd2266de595bcda4ba465b411a2653) fix: Configure docker-compose to match requirements
- [`9298e6a`](https://github.com/Dokploy/templates/commit/9298e6af834b2f05461211fde0291cd3b92da013) fix: Process meta
- [`fff5ac0`](https://github.com/Dokploy/templates/commit/fff5ac0c101b28257a7fc22c4a79fb82e8beefd2) fix: Change logo name
- [`ca6edf5`](https://github.com/Dokploy/templates/commit/ca6edf550c88dbc82a0bb0a1e58141bf078c8769) fix: Remove incorrect mounts
- [`45047db`](https://github.com/Dokploy/templates/commit/45047db4d76bfd3ceef37af5815b7c85de72e1cf) fix: Expose 80 port instead of direct mapping
- [`1c7e228`](https://github.com/Dokploy/templates/commit/1c7e228cea2fb289bce66adc0d61daefe8aee536) fix: Change nginx cache keys default zone size and correct format negotiation
- [`6e87226`](https://github.com/Dokploy/templates/commit/6e87226fe47c3fc3f712e0c9c86b301e1a487834) fix: Escaping
### 📊 Changes
**4 files changed** (+169 additions, -18 deletions)
<details>
<summary>View changed files</summary>
➕ `blueprints/imgproxy/docker-compose.yml` (+76 -0)
➕ `blueprints/imgproxy/imgproxy.png` (+0 -0)
➕ `blueprints/imgproxy/template.toml` (+56 -0)
📝 `meta.json` (+37 -18)
</details>
### 📄 Description
## What is this PR about?
New PR of imgproxy - fast and secure on the fly image processing
## Checklist
Before submitting this PR, please make sure that:
- [x] 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
- [x] I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
- [x] 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
<!-- greptile_comment -->
<h3>Greptile Summary</h3>
This PR adds a new imgproxy template for fast and secure on-the-fly image processing. The implementation includes a two-service setup with imgproxy for image processing and nginx as a caching reverse proxy.
**Key changes:**
- Added `blueprints/imgproxy/` with `docker-compose.yml`, `template.toml`, and logo
- Created properly configured environment variables with secure defaults (key/salt using `${hash:128}`)
- Implemented nginx caching layer with configurable cache settings
- Updated `meta.json` with correct metadata and proper alphabetical ordering
- Used appropriate Docker image versions (imgproxy v3.30.1, nginx 1.28.2-alpine)
**Issues found:**
- The `nginx` service uses `ports` instead of `expose`, which violates template requirements (AGENTS.md line 150)
- The `imgproxy` service should explicitly declare `expose: - 8080` for documentation
<h3>Confidence Score: 4/5</h3>
- This PR is largely safe to merge with minor syntax corrections needed
- The template follows most best practices with proper versioning, secure variable generation, and good architecture. However, it uses `ports` instead of `expose` in the nginx service, which violates documented template requirements. Once this syntax issue is corrected, the template will be production-ready.
- Pay attention to `blueprints/imgproxy/docker-compose.yml` - needs `ports` changed to `expose`
<sub>Last reviewed commit: ca6edf5</sub>
<!-- greptile_other_comments_section -->
<sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub>
**Context used:**
- Context from `dashboard` - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2))
<!-- /greptile_comment -->
---
<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/714
Author: @vladyslavprosolupov
Created: 2/19/2026
Status: ✅ Merged
Merged: 3/5/2026
Merged by: @Siumauricio
Base:
canary← Head:canary📝 Commits (8)
0e58d08feat: Add imgproxy template5da44defix: Configure docker-compose to match requirements9298e6afix: Process metafff5ac0fix: Change logo nameca6edf5fix: Remove incorrect mounts45047dbfix: Expose 80 port instead of direct mapping1c7e228fix: Change nginx cache keys default zone size and correct format negotiation6e87226fix: Escaping📊 Changes
4 files changed (+169 additions, -18 deletions)
View changed files
➕
blueprints/imgproxy/docker-compose.yml(+76 -0)➕
blueprints/imgproxy/imgproxy.png(+0 -0)➕
blueprints/imgproxy/template.toml(+56 -0)📝
meta.json(+37 -18)📄 Description
What is this PR about?
New PR of imgproxy - fast and secure on the fly image processing
Checklist
Before submitting this PR, please make sure that:
Issues related (if applicable)
Close automatically the related issues using the keywords:
closes #ISSUE_NUMBERScreenshots or Videos
Greptile Summary
This PR adds a new imgproxy template for fast and secure on-the-fly image processing. The implementation includes a two-service setup with imgproxy for image processing and nginx as a caching reverse proxy.
Key changes:
blueprints/imgproxy/withdocker-compose.yml,template.toml, and logo${hash:128})meta.jsonwith correct metadata and proper alphabetical orderingIssues found:
nginxservice usesportsinstead ofexpose, which violates template requirements (AGENTS.md line 150)imgproxyservice should explicitly declareexpose: - 8080for documentationConfidence Score: 4/5
portsinstead ofexposein the nginx service, which violates documented template requirements. Once this syntax issue is corrected, the template will be production-ready.blueprints/imgproxy/docker-compose.yml- needsportschanged toexposeLast reviewed commit:
ca6edf5(2/5) Greptile learns from your feedback when you react with thumbs up/down!
Context used:
dashboard- AGENTS.md (source)🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.