[PR #1006] [MERGED] fix: add Databasus template (Postgresus was renamed upstream) #16314

Closed
opened 2026-07-14 23:18:58 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/1006
Author: @Siumauricio
Created: 7/14/2026
Status: Merged
Merged: 7/14/2026
Merged by: @Siumauricio

Base: canaryHead: fix/databasus-rename


📝 Commits (1)

  • cd16441 fix: add databasus (postgresus renamed upstream)

📊 Changes

6 files changed (+69 additions, -5 deletions)

View changed files

blueprints/databasus/databasus.svg (+12 -0)
blueprints/databasus/docker-compose.yml (+22 -0)
blueprints/databasus/meta.json (+17 -0)
blueprints/databasus/template.toml (+11 -0)
📝 blueprints/postgresus/docker-compose.yml (+3 -1)
📝 blueprints/postgresus/meta.json (+4 -4)

📄 Description

Summary

The Postgresus project was renamed upstream to Databasus:

  • https://github.com/RostislavDugin/postgresus now returns a 301 redirect to https://github.com/databasus/databasus
  • The new Docker image is databasus/databasus (currently at v3.49.0); the old rostislavdugin/postgresus image is frozen at its final release v2.15.3
  • The old website postgresus.com no longer resolves (TLS failure); the project now lives at https://databasus.com

Changes

New template: blueprints/databasus/

  • docker-compose.yml using databasus/databasus:latest, port 4005, persistent volume at /databasus-data, and the upstream-recommended databasus healthcheck healthcheck
  • meta.json with the new repo/website/docs links and the official square logo from the upstream repo (assets/logo-square.svg)
  • template.toml exposing the UI domain on port 4005

Updated template: blueprints/postgresus/ (kept, deprecated)

The old image still exists on Docker Hub, so instead of deleting the template (which would break discoverability for existing users) it was kept minimally working:

  • Image pinned to its final release rostislavdugin/postgresus:v2.15.3 (the latest tag is frozen and will never receive updates)
  • meta.json description now marks it as deprecated and points users to the Databasus template; dead postgresus.com links replaced with databasus.com
  • A comment in the compose file explains the rename

If maintainers prefer to remove the old template entirely instead, happy to drop the blueprints/postgresus/ folder in this PR.

Verification

Deployed the new databasus template on a live Dokploy instance:

  • Deploy completed in ~20s
  • UI reachable over the generated domain with HTTP 200, page title: Databasus - databases backups (PostgreSQL, MySQL, MongoDB)
  • node build-scripts/generate-meta.js --check passes (477 templates validated)

Closes #666

🤖 Generated with Claude Code


🔄 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/1006 **Author:** [@Siumauricio](https://github.com/Siumauricio) **Created:** 7/14/2026 **Status:** ✅ Merged **Merged:** 7/14/2026 **Merged by:** [@Siumauricio](https://github.com/Siumauricio) **Base:** `canary` ← **Head:** `fix/databasus-rename` --- ### 📝 Commits (1) - [`cd16441`](https://github.com/Dokploy/templates/commit/cd164419014610b920d87a3b37f589514316c9d7) fix: add databasus (postgresus renamed upstream) ### 📊 Changes **6 files changed** (+69 additions, -5 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/databasus/databasus.svg` (+12 -0) ➕ `blueprints/databasus/docker-compose.yml` (+22 -0) ➕ `blueprints/databasus/meta.json` (+17 -0) ➕ `blueprints/databasus/template.toml` (+11 -0) 📝 `blueprints/postgresus/docker-compose.yml` (+3 -1) 📝 `blueprints/postgresus/meta.json` (+4 -4) </details> ### 📄 Description ## Summary The Postgresus project was renamed upstream to **Databasus**: - `https://github.com/RostislavDugin/postgresus` now returns a **301 redirect** to https://github.com/databasus/databasus - The new Docker image is `databasus/databasus` (currently at v3.49.0); the old `rostislavdugin/postgresus` image is frozen at its final release **v2.15.3** - The old website `postgresus.com` no longer resolves (TLS failure); the project now lives at https://databasus.com ## Changes ### New template: `blueprints/databasus/` - `docker-compose.yml` using `databasus/databasus:latest`, port 4005, persistent volume at `/databasus-data`, and the upstream-recommended `databasus healthcheck` healthcheck - `meta.json` with the new repo/website/docs links and the official square logo from the upstream repo (`assets/logo-square.svg`) - `template.toml` exposing the UI domain on port 4005 ### Updated template: `blueprints/postgresus/` (kept, deprecated) The old image still exists on Docker Hub, so instead of deleting the template (which would break discoverability for existing users) it was kept minimally working: - Image pinned to its final release `rostislavdugin/postgresus:v2.15.3` (the `latest` tag is frozen and will never receive updates) - `meta.json` description now marks it as **deprecated** and points users to the Databasus template; dead `postgresus.com` links replaced with `databasus.com` - A comment in the compose file explains the rename If maintainers prefer to remove the old template entirely instead, happy to drop the `blueprints/postgresus/` folder in this PR. ## Verification Deployed the new `databasus` template on a live Dokploy instance: - Deploy completed in ~20s - UI reachable over the generated domain with **HTTP 200**, page title: `Databasus - databases backups (PostgreSQL, MySQL, MongoDB)` - `node build-scripts/generate-meta.js --check` passes (477 templates validated) Closes #666 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <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-07-14 23:18:58 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#16314