github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-07-15 14:52:05 -05:00
Code Issues 2.9k Packages Projects Releases Wiki Activity

[PR #900] [MERGED] feat: add wallabag template #15235

New Issue
Closed
opened 2026-07-13 16:57:23 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-07-13 16:57:23 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/900
Author: @NightVibes33
Created: 5/21/2026
Status: ✅ Merged
Merged: 7/8/2026
Merged by: @Siumauricio

Base: canary ← Head: add-wallabag-template

📝 Commits (3)

  • 455e191 feat: add wallabag template
  • d7d426c Merge remote-tracking branch 'origin/canary' into add-wallabag-template
  • 65a9a0a fix: let wallabag entrypoint provision the database so the install runs

📊 Changes

4 files changed (+107 additions, -0 deletions)

View changed files

➕ blueprints/wallabag/docker-compose.yml (+64 -0)
➕ blueprints/wallabag/meta.json (+18 -0)
➕ blueprints/wallabag/template.toml (+20 -0)
➕ blueprints/wallabag/wallabag.svg (+5 -0)

📄 Description

/claim #152

Summary

Adds a wallabag Dokploy template as a separate focused PR:

  • wallabag 2.6.14 web service exposed on port 80
  • MariaDB 11.4 backend with generated root/app database passwords
  • Redis cache service with persistent storage
  • persistent image uploads volume
  • domain, server name, and sender email wiring through template.toml
  • metadata and SVG icon entry in meta.json

Review notes

  • kept separate from #883 so the larger template PR stays focused and this one can be reviewed independently
  • follows the official wallabag Docker MariaDB + Redis example while adapting it to Dokploy conventions: no container_name, no explicit networks, and no host port mappings
  • official reference: https://github.com/wallabag/docker#docker-compose

Verification

  • GitHub Actions validate-docker-compose: passing
  • GitHub Actions validate: passing
  • GitHub Actions build-preview: passing
  • GitHub Actions validate-meta: passing
  • node dedupe-and-sort-meta.js
  • local TOML/YAML structural validation for this template: compose parses, configured domain service exists, domain port is valid, meta.json entry exists, and the template does not use container_name, explicit networks, or host port mappings
  • git diff --check

🔄 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/900 **Author:** [@NightVibes33](https://github.com/NightVibes33) **Created:** 5/21/2026 **Status:** ✅ Merged **Merged:** 7/8/2026 **Merged by:** [@Siumauricio](https://github.com/Siumauricio) **Base:** `canary` ← **Head:** `add-wallabag-template` --- ### 📝 Commits (3) - [`455e191`](https://github.com/Dokploy/templates/commit/455e1914a9eeabb0d38213e056ef3b41bd159784) feat: add wallabag template - [`d7d426c`](https://github.com/Dokploy/templates/commit/d7d426c968454f941919d1990793f36e155044e8) Merge remote-tracking branch 'origin/canary' into add-wallabag-template - [`65a9a0a`](https://github.com/Dokploy/templates/commit/65a9a0a5a5f9bb5d626b254f4a65deed78ec2ee9) fix: let wallabag entrypoint provision the database so the install runs ### 📊 Changes **4 files changed** (+107 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/wallabag/docker-compose.yml` (+64 -0) ➕ `blueprints/wallabag/meta.json` (+18 -0) ➕ `blueprints/wallabag/template.toml` (+20 -0) ➕ `blueprints/wallabag/wallabag.svg` (+5 -0) </details> ### 📄 Description /claim #152 ## Summary Adds a wallabag Dokploy template as a separate focused PR: - wallabag `2.6.14` web service exposed on port 80 - MariaDB 11.4 backend with generated root/app database passwords - Redis cache service with persistent storage - persistent image uploads volume - domain, server name, and sender email wiring through `template.toml` - metadata and SVG icon entry in `meta.json` ## Review notes - kept separate from #883 so the larger template PR stays focused and this one can be reviewed independently - follows the official wallabag Docker MariaDB + Redis example while adapting it to Dokploy conventions: no `container_name`, no explicit networks, and no host port mappings - official reference: https://github.com/wallabag/docker#docker-compose ## Verification - GitHub Actions `validate-docker-compose`: passing - GitHub Actions `validate`: passing - GitHub Actions `build-preview`: passing - GitHub Actions `validate-meta`: passing - `node dedupe-and-sort-meta.js` - local TOML/YAML structural validation for this template: compose parses, configured domain service exists, domain port is valid, `meta.json` entry exists, and the template does not use `container_name`, explicit networks, or host port mappings - `git diff --check` --- <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-13 16:57:23 -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#15235
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?