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 MaxIO template — a lightweight, S3-compatible object storage server written in Rust — to the Dokploy templates collection. While the intent is correct, there are several critical issues that need to be addressed before merging.
docker-compose.yml: Missing required version: "3.8", uses ports (must be replaced with expose), missing restart: unless-stopped, and the image is not pinned to a specific version tag — all of which violate the repository's documented conventions.
template.toml: Env vars are declared using TOML table syntax ([config.env] with key-value pairs) instead of the required array-of-strings format under [config]. This will cause env variables to be silently ignored at deploy time.
meta.json: The Strapi template entry is unintentionally deleted while its blueprint files still exist in the repository. This is likely a merge conflict artifact and must be restored.
The logo is provided as PNG rather than the preferred SVG format (minor).
Confidence Score: 1/5
Not safe to merge — multiple convention violations in the template files and an unintended deletion of an existing template.
The docker-compose.yml violates three hard requirements (version, ports vs expose, restart), the template.toml uses the wrong env var format which would break deployment, and the PR accidentally removes the Strapi entry from meta.json.
blueprints/maxio/docker-compose.yml, blueprints/maxio/template.toml, and meta.json all require fixes before this PR can be merged.
This PR removes the strapi entry from meta.json, but the blueprint files (blueprints/strapi/docker-compose.yml, blueprints/strapi/template.toml, blueprints/strapi/strapi.svg) still exist in the repository. This deletion appears to be an unintended side-effect, likely from a merge conflict or editing error. The Strapi entry should be restored so that this PR only adds the MaxIO template.
🔄 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/744
**Author:** [@sancho1952007](https://github.com/sancho1952007)
**Created:** 3/12/2026
**Status:** 🔄 Open
**Base:** `canary` ← **Head:** `add/maxio`
---
### 📝 Commits (9)
- [`2028969`](https://github.com/Dokploy/templates/commit/2028969f96c5325221d7e8e76b56cb68d054ce3f) Add Docker Compose configuration for Maxio service
- [`115bdd2`](https://github.com/Dokploy/templates/commit/115bdd2fdd3053c37ce4319ae463d0ecb8b3f35a) Add template configuration for maxio service
- [`4108ae2`](https://github.com/Dokploy/templates/commit/4108ae2d8e13a7da1a18af36308ebb054967e8d6) Add Maxio logo
- [`c9976c7`](https://github.com/Dokploy/templates/commit/c9976c7625b3aea91c9c0d9c4d371dee2843951f) Add Maxio metadata to meta.json
- [`6db517e`](https://github.com/Dokploy/templates/commit/6db517ebd59036f86515d0fd51345f831de7f4ba) Run node dedupe-and-sort-meta.js
- [`06f8b45`](https://github.com/Dokploy/templates/commit/06f8b45bad2f0d76785e53b493a52de541a98035) Fix name from Maxio to MaxIO
- [`3b04651`](https://github.com/Dokploy/templates/commit/3b04651097343e254e65c6edc7028e1724e559af) Make suggested updates
- [`616d08c`](https://github.com/Dokploy/templates/commit/616d08ce66d9eb27f4947cb8ed8107a8cf9b58fb) Add missing restart policy
- [`1955d94`](https://github.com/Dokploy/templates/commit/1955d94f06ef02aa5b4525cefbf21c9c8da9b812) Make improvements
### 📊 Changes
**4 files changed** (+50 additions, -18 deletions)
<details>
<summary>View changed files</summary>
➕ `blueprints/maxio/docker-compose.yml` (+15 -0)
➕ `blueprints/maxio/maxio.svg` (+8 -0)
➕ `blueprints/maxio/template.toml` (+10 -0)
📝 `meta.json` (+17 -18)
</details>
### 📄 Description
## What is this PR about?
New PR of [MaxIO](https://github.com/coollabsio/maxio)
## 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.
- [ ] 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 MaxIO template — a lightweight, S3-compatible object storage server written in Rust — to the Dokploy templates collection. While the intent is correct, there are several critical issues that need to be addressed before merging.
- **`docker-compose.yml`**: Missing required `version: "3.8"`, uses `ports` (must be replaced with `expose`), missing `restart: unless-stopped`, and the image is not pinned to a specific version tag — all of which violate the repository's documented conventions.
- **`template.toml`**: Env vars are declared using TOML table syntax (`[config.env]` with key-value pairs) instead of the required array-of-strings format under `[config]`. This will cause env variables to be silently ignored at deploy time.
- **`meta.json`**: The Strapi template entry is unintentionally deleted while its blueprint files still exist in the repository. This is likely a merge conflict artifact and must be restored.
- The logo is provided as PNG rather than the preferred SVG format (minor).
<h3>Confidence Score: 1/5</h3>
- Not safe to merge — multiple convention violations in the template files and an unintended deletion of an existing template.
- The `docker-compose.yml` violates three hard requirements (`version`, `ports` vs `expose`, `restart`), the `template.toml` uses the wrong env var format which would break deployment, and the PR accidentally removes the Strapi entry from `meta.json`.
- `blueprints/maxio/docker-compose.yml`, `blueprints/maxio/template.toml`, and `meta.json` all require fixes before this PR can be merged.
<!-- greptile_failed_comments -->
<details><summary><h3>Comments Outside Diff (1)</h3></summary>
1. `meta.json`, line 5969-5985 ([link](https://github.com/dokploy/templates/blob/06f8b45bad2f0d76785e53b493a52de541a98035/meta.json#L5969-L5985))
**Unrelated deletion of the Strapi template**
This PR removes the `strapi` entry from `meta.json`, but the blueprint files (`blueprints/strapi/docker-compose.yml`, `blueprints/strapi/template.toml`, `blueprints/strapi/strapi.svg`) still exist in the repository. This deletion appears to be an unintended side-effect, likely from a merge conflict or editing error. The Strapi entry should be restored so that this PR only adds the MaxIO template.
</details>
<!-- /greptile_failed_comments -->
<sub>Last reviewed commit: 06f8b45</sub>
> Greptile also left **3 inline comments** on this PR.
<sub>(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!</sub>
**Context used:**
- Rule used - 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/744
Author: @sancho1952007
Created: 3/12/2026
Status: 🔄 Open
Base:
canary← Head:add/maxio📝 Commits (9)
2028969Add Docker Compose configuration for Maxio service115bdd2Add template configuration for maxio service4108ae2Add Maxio logoc9976c7Add Maxio metadata to meta.json6db517eRun node dedupe-and-sort-meta.js06f8b45Fix name from Maxio to MaxIO3b04651Make suggested updates616d08cAdd missing restart policy1955d94Make improvements📊 Changes
4 files changed (+50 additions, -18 deletions)
View changed files
➕
blueprints/maxio/docker-compose.yml(+15 -0)➕
blueprints/maxio/maxio.svg(+8 -0)➕
blueprints/maxio/template.toml(+10 -0)📝
meta.json(+17 -18)📄 Description
What is this PR about?
New PR of MaxIO
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 MaxIO template — a lightweight, S3-compatible object storage server written in Rust — to the Dokploy templates collection. While the intent is correct, there are several critical issues that need to be addressed before merging.
docker-compose.yml: Missing requiredversion: "3.8", usesports(must be replaced withexpose), missingrestart: unless-stopped, and the image is not pinned to a specific version tag — all of which violate the repository's documented conventions.template.toml: Env vars are declared using TOML table syntax ([config.env]with key-value pairs) instead of the required array-of-strings format under[config]. This will cause env variables to be silently ignored at deploy time.meta.json: The Strapi template entry is unintentionally deleted while its blueprint files still exist in the repository. This is likely a merge conflict artifact and must be restored.Confidence Score: 1/5
docker-compose.ymlviolates three hard requirements (version,portsvsexpose,restart), thetemplate.tomluses the wrong env var format which would break deployment, and the PR accidentally removes the Strapi entry frommeta.json.blueprints/maxio/docker-compose.yml,blueprints/maxio/template.toml, andmeta.jsonall require fixes before this PR can be merged.Comments Outside Diff (1)
meta.json, line 5969-5985 (link)Unrelated deletion of the Strapi template
This PR removes the
strapientry frommeta.json, but the blueprint files (blueprints/strapi/docker-compose.yml,blueprints/strapi/template.toml,blueprints/strapi/strapi.svg) still exist in the repository. This deletion appears to be an unintended side-effect, likely from a merge conflict or editing error. The Strapi entry should be restored so that this PR only adds the MaxIO template.Last reviewed commit:
06f8b45(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!
Context used:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.