Update autobase console image tag in blueprints/autobase/docker-compose.yml from 2.5.2 to 2.7.2 and bump the corresponding package version in meta.json to 2.7.2 to keep metadata in sync with the deployed image.
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
Now with the built-in SQL editor
Greptile Summary
This PR updates the Autobase template from version 2.5.2 to 2.7.2 by bumping the autobase/console image tag in docker-compose.yml and the corresponding version in meta.json. It also adds the new dbdesk_studio_data named volume (required by the 2.7.x image for the built-in SQL editor), correctly declared at both the service and top-level volumes: sections.
Confidence Score: 5/5
Safe to merge — a straightforward version bump with correct volume declaration.
All changes are correct: the image tag and meta.json version are in sync, the new named volume is properly declared at both the service and top-level, and no regressions are introduced. The previous P1 finding (missing top-level volume declaration) has been resolved in this revision.
No files require special attention.
Comments Outside Diff (1)
blueprints/autobase/docker-compose.yml, line 17-19 (link)
Missing top-level volume declaration for dbdesk_studio_data
The new named volume dbdesk_studio_data is referenced in the service's volumes: list but is not declared in the top-level volumes: section. Docker Compose will refuse to start with: Named volume "dbdesk_studio_data:/opt/dbdesk-studio:rw" is used in service "autobase-console" but no declaration was found in the volumes section.
🔄 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/830
**Author:** [@vitabaks](https://github.com/vitabaks)
**Created:** 4/28/2026
**Status:** 🔄 Open
**Base:** `canary` ← **Head:** `autobase-2-7`
---
### 📝 Commits (2)
- [`19e0ed1`](https://github.com/Dokploy/templates/commit/19e0ed1912f1abcf48a559334d255e4736027369) Update Autobase to version 2.7
- [`224ebe9`](https://github.com/Dokploy/templates/commit/224ebe90ee1e299d1b387d7dd9270dce678566ce) Add dbdesk_studio_data Docker volume
### 📊 Changes
**2 files changed** (+4 additions, -2 deletions)
<details>
<summary>View changed files</summary>
📝 `blueprints/autobase/docker-compose.yml` (+3 -1)
📝 `meta.json` (+1 -1)
</details>
### 📄 Description
Update autobase console image tag in blueprints/autobase/docker-compose.yml from 2.5.2 to 2.7.2 and bump the corresponding package version in meta.json to 2.7.2 to keep metadata in sync with the deployed image.
Release notes: https://github.com/vitabaks/autobase/releases/tag/2.7.0
## What is this PR about?
New PR of [Template Name]
## 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
- [ ] 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
Now with the built-in SQL editor
<img width="3496" height="2020" alt="2026-04-04_14-47-41" src="https://github.com/user-attachments/assets/2aa551ca-c311-4359-8306-ed779067d473" />
<!-- greptile_comment -->
<h3>Greptile Summary</h3>
This PR updates the Autobase template from version 2.5.2 to 2.7.2 by bumping the `autobase/console` image tag in `docker-compose.yml` and the corresponding version in `meta.json`. It also adds the new `dbdesk_studio_data` named volume (required by the 2.7.x image for the built-in SQL editor), correctly declared at both the service and top-level `volumes:` sections.
<h3>Confidence Score: 5/5</h3>
Safe to merge — a straightforward version bump with correct volume declaration.
All changes are correct: the image tag and meta.json version are in sync, the new named volume is properly declared at both the service and top-level, and no regressions are introduced. The previous P1 finding (missing top-level volume declaration) has been resolved in this revision.
No files require special attention.
<!-- greptile_failed_comments -->
<details><summary><h3>Comments Outside Diff (1)</h3></summary>
1. `blueprints/autobase/docker-compose.yml`, line 17-19 ([link](https://github.com/dokploy/templates/blob/19e0ed1912f1abcf48a559334d255e4736027369/blueprints/autobase/docker-compose.yml#L17-L19))
<a href="#"><img alt="P1" src="https://greptile-static-assets.s3.amazonaws.com/badges/p1.svg?v=7" align="top"></a> **Missing top-level volume declaration for `dbdesk_studio_data`**
The new named volume `dbdesk_studio_data` is referenced in the service's `volumes:` list but is not declared in the top-level `volumes:` section. Docker Compose will refuse to start with: `Named volume "dbdesk_studio_data:/opt/dbdesk-studio:rw" is used in service "autobase-console" but no declaration was found in the volumes section.`
</details>
<!-- /greptile_failed_comments -->
<sub>Reviews (2): Last reviewed commit: ["Add dbdesk\_studio\_data Docker volume"](https://github.com/dokploy/templates/commit/224ebe90ee1e299d1b387d7dd9270dce678566ce) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=30068720)</sub>
<!-- /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/830
Author: @vitabaks
Created: 4/28/2026
Status: 🔄 Open
Base:
canary← Head:autobase-2-7📝 Commits (2)
19e0ed1Update Autobase to version 2.7224ebe9Add dbdesk_studio_data Docker volume📊 Changes
2 files changed (+4 additions, -2 deletions)
View changed files
📝
blueprints/autobase/docker-compose.yml(+3 -1)📝
meta.json(+1 -1)📄 Description
Update autobase console image tag in blueprints/autobase/docker-compose.yml from 2.5.2 to 2.7.2 and bump the corresponding package version in meta.json to 2.7.2 to keep metadata in sync with the deployed image.
Release notes: https://github.com/vitabaks/autobase/releases/tag/2.7.0
What is this PR about?
New PR of [Template Name]
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
Now with the built-in SQL editor
Greptile Summary
This PR updates the Autobase template from version 2.5.2 to 2.7.2 by bumping the
autobase/consoleimage tag indocker-compose.ymland the corresponding version inmeta.json. It also adds the newdbdesk_studio_datanamed volume (required by the 2.7.x image for the built-in SQL editor), correctly declared at both the service and top-levelvolumes:sections.Confidence Score: 5/5
Safe to merge — a straightforward version bump with correct volume declaration.
All changes are correct: the image tag and meta.json version are in sync, the new named volume is properly declared at both the service and top-level, and no regressions are introduced. The previous P1 finding (missing top-level volume declaration) has been resolved in this revision.
No files require special attention.
Comments Outside Diff (1)
blueprints/autobase/docker-compose.yml, line 17-19 (link)dbdesk_studio_dataThe new named volume
dbdesk_studio_datais referenced in the service'svolumes:list but is not declared in the top-levelvolumes:section. Docker Compose will refuse to start with:Named volume "dbdesk_studio_data:/opt/dbdesk-studio:rw" is used in service "autobase-console" but no declaration was found in the volumes section.Reviews (2): Last reviewed commit: "Add dbdesk_studio_data Docker volume" | Re-trigger Greptile
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.