github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-05-06 10:37:26 -05:00
Code Issues 990 Packages Projects Releases Wiki Activity

[PR #786] feat(: add wallabag blueprint #2900

New Issue
Open
opened 2026-04-23 03:37:53 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-23 03:37:53 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/786
Author: @StellarRounin
Created: 4/12/2026
Status: 🔄 Open

Base: canary ← Head: template-wallabag

📝 Commits (10+)

  • 997fb4e feat(: add wallabag blueprint
  • cc81777 fix: Add version & restart
  • 1c18c7f fix: add description to meta json
  • ac1f131 fix: Fix env & port in template toml
  • f28a263 fix: Image
  • 5bb5f85 fix: Change password string for helper
  • fb8fb08 fix: Change domain string for helper
  • eef4c57 fix: Change absolute for relative paths
  • 186de04 fix: Add specific verision to meta.json
  • 169a06c fix

📊 Changes

4 files changed (+79 additions, -18 deletions)

View changed files

➕ blueprints/wallabag/docker-compose.yml (+46 -0)
➕ blueprints/wallabag/template.toml (+15 -0)
➕ blueprints/wallabag/wallabag.png (+0 -0)
📝 meta.json (+18 -18)

📄 Description

What is this PR about?

New PR of Wallabag

This PR:

  • adds a new wallabag blueprint with docker-compose.yml, template.toml, and logo.svg
  • adds the wallabag entry to meta.json

Screenshots or Videos

Greptile Summary

This PR adds a Wallabag blueprint with previous review issues largely addressed (version, restart policy, relative paths, credentials), but three blocking issues remain. The template.toml incorrectly places DB_PASSWORD, ROOT_PASSWORD, and the missing DOMAIN mapping inside [[config.domains]] instead of a [config.env] table, so none of these variables will be substituted in docker-compose.yml. The wallabag/wallabag image is unpinned while meta.json declares version 2.6.14. Finally, the Strapi entry has been accidentally deleted from meta.json, likely due to a rebase conflict.

Confidence Score: 3/5

Not safe to merge — broken env config prevents database auth and domain routing, and Strapi is accidentally deleted from the registry.

Three P1 issues: the env variable misconfiguration in template.toml breaks the primary user path (DB auth fails, domain redirect fails); the wallabag image is unpinned counter to the version declared in meta.json; and the Strapi entry deletion from meta.json is an unintended regression. These need to be resolved before merging.

blueprints/wallabag/template.toml (env variable structure), blueprints/wallabag/docker-compose.yml (pinned image version), meta.json (restore Strapi entry)

Reviews (2): Last reviewed commit: "fix: Delete duplicate strapi from meta j..." | Re-trigger Greptile

Greptile also left 1 inline comment on this PR.

Context used:

  • Context used - AGENTS.md (source)

🔄 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/786 **Author:** [@StellarRounin](https://github.com/StellarRounin) **Created:** 4/12/2026 **Status:** 🔄 Open **Base:** `canary` ← **Head:** `template-wallabag` --- ### 📝 Commits (10+) - [`997fb4e`](https://github.com/Dokploy/templates/commit/997fb4ee7e22e67c3b89f26450f1bb2003f316ec) feat(: add wallabag blueprint - [`cc81777`](https://github.com/Dokploy/templates/commit/cc81777a24ec42b461ab72f507c67b505d3df89f) fix: Add version & restart - [`1c18c7f`](https://github.com/Dokploy/templates/commit/1c18c7f15900a0000abe0c50c356fd5c34847bc1) fix: add description to meta json - [`ac1f131`](https://github.com/Dokploy/templates/commit/ac1f131973e1c1da13a410835c2b2386a507977b) fix: Fix env & port in template toml - [`f28a263`](https://github.com/Dokploy/templates/commit/f28a263cf0f3e0bf5b3c60569e0387d1e6aff729) fix: Image - [`5bb5f85`](https://github.com/Dokploy/templates/commit/5bb5f853f8a1e0fca08e211e1956603a4fbe4974) fix: Change password string for helper - [`fb8fb08`](https://github.com/Dokploy/templates/commit/fb8fb08770f0cca43baff057b998a5453247fcb4) fix: Change domain string for helper - [`eef4c57`](https://github.com/Dokploy/templates/commit/eef4c57f79c0a1f2103f5dc06d7c7a7c2818a913) fix: Change absolute for relative paths - [`186de04`](https://github.com/Dokploy/templates/commit/186de04aed807f2baa39b7e04169a051a95281e0) fix: Add specific verision to meta.json - [`169a06c`](https://github.com/Dokploy/templates/commit/169a06cf45d81d76f7296b41a5205ac30d920aaf) fix ### 📊 Changes **4 files changed** (+79 additions, -18 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/wallabag/docker-compose.yml` (+46 -0) ➕ `blueprints/wallabag/template.toml` (+15 -0) ➕ `blueprints/wallabag/wallabag.png` (+0 -0) 📝 `meta.json` (+18 -18) </details> ### 📄 Description ## What is this PR about? New PR of Wallabag This PR: - adds a new wallabag blueprint with docker-compose.yml, template.toml, and logo.svg - adds the wallabag entry to meta.json ## Screenshots or Videos <!-- greptile_comment --> <h3>Greptile Summary</h3> This PR adds a Wallabag blueprint with previous review issues largely addressed (version, restart policy, relative paths, credentials), but three blocking issues remain. The `template.toml` incorrectly places `DB_PASSWORD`, `ROOT_PASSWORD`, and the missing `DOMAIN` mapping inside `[[config.domains]]` instead of a `[config.env]` table, so none of these variables will be substituted in `docker-compose.yml`. The `wallabag/wallabag` image is unpinned while `meta.json` declares version `2.6.14`. Finally, the Strapi entry has been accidentally deleted from `meta.json`, likely due to a rebase conflict. <h3>Confidence Score: 3/5</h3> Not safe to merge — broken env config prevents database auth and domain routing, and Strapi is accidentally deleted from the registry. Three P1 issues: the env variable misconfiguration in template.toml breaks the primary user path (DB auth fails, domain redirect fails); the wallabag image is unpinned counter to the version declared in meta.json; and the Strapi entry deletion from meta.json is an unintended regression. These need to be resolved before merging. blueprints/wallabag/template.toml (env variable structure), blueprints/wallabag/docker-compose.yml (pinned image version), meta.json (restore Strapi entry) <sub>Reviews (2): Last reviewed commit: ["fix: Delete duplicate strapi from meta j..."](https://github.com/dokploy/templates/commit/8ae670edeafba626d26dc01e925e2ca2886dccea) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=28148639)</sub> > Greptile also left **1 inline comment** on this PR. **Context used:** - Context 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>
GiteaMirror added the pull-request label 2026-04-23 03:37:53 -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#2900
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?