github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-05-06 02:07:03 -05:00
Code Issues 990 Packages Projects Releases Wiki Activity

[PR #714] [MERGED] feat: Add imgproxy template #2036

New Issue
Closed
opened 2026-04-20 11:03:43 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 11:03:43 -05:00
Owner
Copy Link

📋 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)

  • 0e58d08 feat: Add imgproxy template
  • 5da44de fix: Configure docker-compose to match requirements
  • 9298e6a fix: Process meta
  • fff5ac0 fix: Change logo name
  • ca6edf5 fix: Remove incorrect mounts
  • 45047db fix: Expose 80 port instead of direct mapping
  • 1c7e228 fix: Change nginx cache keys default zone size and correct format negotiation
  • 6e87226 fix: 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_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

Last reviewed commit: ca6edf5

(2/5) Greptile learns from your feedback when you react with thumbs up/down!

Context used:

  • Context from dashboard - AGENTS.md (source)

🔄 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>
GiteaMirror added the pull-request label 2026-04-20 11:03:43 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
pull-request
Mirrored from GitHub Pull Request
 template
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#2036
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?