configurator (alpine:3.20) — Generates rclone.conf for Cloudflare R2 (runs once and exits)
backup (ttionya/vaultwarden-backup:1.26.2) — Scheduled backups via cron
Features
Auto-generated admin token and backup ZIP password
Configurable backup schedule (default: daily at 5 AM UTC)
Configurable backup retention (default: 30 days)
Full SMTP configuration for email notifications/invitations
Configurable timezone (default: UTC)
All Cloudflare R2 credentials exposed as environment variables
Checklist
All Docker images pinned to specific versions (no latest)
All images verified with docker manifest inspect
No ports, container_name, or networks in docker-compose.yml
meta.json entry added and processed with dedupe-and-sort-meta.js
Logo file included
Template ID matches folder name
Greptile Summary
Adds a new Vaultwarden template with automated Cloudflare R2 backups using a three-service architecture: the main password manager, a one-time configurator for rclone setup, and a scheduled backup service.
Key changes:
New vaultwarden-with-backup template with pinned image versions
Auto-generated admin token and backup encryption password
Configurable backup schedule (cron) and retention period
Full SMTP support for email notifications
Cloudflare R2 integration for remote backups
Proper meta.json entry with sorted placement
Issues found:
Missing required version: "3.8" field at the top of docker-compose.yml
Confidence Score: 4/5
This PR is safe to merge after fixing the missing version field
The template follows best practices with pinned versions, proper secret generation, and good service architecture. The only issue is a missing version: "3.8" field which is required by the project's style guide but is a simple one-line fix. All other aspects (meta.json sorting, logo inclusion, environment variables, volume configuration) are correctly implemented.
blueprints/vaultwarden-with-backup/docker-compose.yml requires the version field to be added
🔄 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/725
**Author:** [@CarlosHugoRodriguezC](https://github.com/CarlosHugoRodriguezC)
**Created:** 2/23/2026
**Status:** 🔄 Open
**Base:** `canary` ← **Head:** `feat/vaultwarden-with-backup`
---
### 📝 Commits (3)
- [`711cd34`](https://github.com/Dokploy/templates/commit/711cd3482ded78357015bc1c03a6b3281ca7ab39) feat: add vaultwarden-with-backup template
- [`1584805`](https://github.com/Dokploy/templates/commit/1584805ffa8b58d53568444c22acabdd0c8af8eb) fix: address PR review feedback for vaultwarden-with-backup
- [`ec354a4`](https://github.com/Dokploy/templates/commit/ec354a4d54973c7ef9def5255684c7ad3e1cc1be) Update blueprints/vaultwarden-with-backup/docker-compose.yml
### 📊 Changes
**4 files changed** (+167 additions, -18 deletions)
<details>
<summary>View changed files</summary>
➕ `blueprints/vaultwarden-with-backup/docker-compose.yml` (+78 -0)
➕ `blueprints/vaultwarden-with-backup/template.toml` (+34 -0)
➕ `blueprints/vaultwarden-with-backup/vaultwarden.svg` (+19 -0)
📝 `meta.json` (+36 -18)
</details>
### 📄 Description
## New Template: vaultwarden-with-backup
Adds a Vaultwarden template with automated backups to Cloudflare R2 storage.
### Services
- **vaultwarden** (`vaultwarden/server:1.34.3`) — Password manager
- **configurator** (`alpine:3.20`) — Generates rclone.conf for Cloudflare R2 (runs once and exits)
- **backup** (`ttionya/vaultwarden-backup:1.26.2`) — Scheduled backups via cron
### Features
- Auto-generated admin token and backup ZIP password
- Configurable backup schedule (default: daily at 5 AM UTC)
- Configurable backup retention (default: 30 days)
- Full SMTP configuration for email notifications/invitations
- Configurable timezone (default: UTC)
- All Cloudflare R2 credentials exposed as environment variables
### Checklist
- [x] All Docker images pinned to specific versions (no `latest`)
- [x] All images verified with `docker manifest inspect`
- [x] No `ports`, `container_name`, or `networks` in docker-compose.yml
- [x] `meta.json` entry added and processed with `dedupe-and-sort-meta.js`
- [x] Logo file included
- [x] Template ID matches folder name
<!-- greptile_comment -->
<h3>Greptile Summary</h3>
Adds a new Vaultwarden template with automated Cloudflare R2 backups using a three-service architecture: the main password manager, a one-time configurator for rclone setup, and a scheduled backup service.
**Key changes:**
- New `vaultwarden-with-backup` template with pinned image versions
- Auto-generated admin token and backup encryption password
- Configurable backup schedule (cron) and retention period
- Full SMTP support for email notifications
- Cloudflare R2 integration for remote backups
- Proper meta.json entry with sorted placement
**Issues found:**
- Missing required `version: "3.8"` field at the top of docker-compose.yml
<h3>Confidence Score: 4/5</h3>
- This PR is safe to merge after fixing the missing version field
- The template follows best practices with pinned versions, proper secret generation, and good service architecture. The only issue is a missing `version: "3.8"` field which is required by the project's style guide but is a simple one-line fix. All other aspects (meta.json sorting, logo inclusion, environment variables, volume configuration) are correctly implemented.
- blueprints/vaultwarden-with-backup/docker-compose.yml requires the version field to be added
<sub>Last reviewed commit: 711cd34</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/725
Author: @CarlosHugoRodriguezC
Created: 2/23/2026
Status: 🔄 Open
Base:
canary← Head:feat/vaultwarden-with-backup📝 Commits (3)
711cd34feat: add vaultwarden-with-backup template1584805fix: address PR review feedback for vaultwarden-with-backupec354a4Update blueprints/vaultwarden-with-backup/docker-compose.yml📊 Changes
4 files changed (+167 additions, -18 deletions)
View changed files
➕
blueprints/vaultwarden-with-backup/docker-compose.yml(+78 -0)➕
blueprints/vaultwarden-with-backup/template.toml(+34 -0)➕
blueprints/vaultwarden-with-backup/vaultwarden.svg(+19 -0)📝
meta.json(+36 -18)📄 Description
New Template: vaultwarden-with-backup
Adds a Vaultwarden template with automated backups to Cloudflare R2 storage.
Services
vaultwarden/server:1.34.3) — Password manageralpine:3.20) — Generates rclone.conf for Cloudflare R2 (runs once and exits)ttionya/vaultwarden-backup:1.26.2) — Scheduled backups via cronFeatures
Checklist
latest)docker manifest inspectports,container_name, ornetworksin docker-compose.ymlmeta.jsonentry added and processed withdedupe-and-sort-meta.jsGreptile Summary
Adds a new Vaultwarden template with automated Cloudflare R2 backups using a three-service architecture: the main password manager, a one-time configurator for rclone setup, and a scheduled backup service.
Key changes:
vaultwarden-with-backuptemplate with pinned image versionsIssues found:
version: "3.8"field at the top of docker-compose.ymlConfidence Score: 4/5
version: "3.8"field which is required by the project's style guide but is a simple one-line fix. All other aspects (meta.json sorting, logo inclusion, environment variables, volume configuration) are correctly implemented.Last reviewed commit:
711cd34(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.