github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-07-16 21:58:44 -05:00
Code Issues 3.0k Packages Projects Releases Wiki Activity

[PR #896] feat: add LubeLogger template #14313

New Issue
Open
opened 2026-06-17 06:29:36 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-06-17 06:29:36 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/896
Author: @100more
Created: 5/21/2026
Status: 🔄 Open

Base: canary ← Head: codex/add-lubelogger-template

📝 Commits (1)

  • dd79917 feat: add LubeLogger template

📊 Changes

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

View changed files

➕ blueprints/lubelogger/docker-compose.yml (+20 -0)
➕ blueprints/lubelogger/lubelogger.png (+0 -0)
➕ blueprints/lubelogger/template.toml (+18 -0)
📝 meta.json (+18 -0)

📄 Description

feat: add LubeLogger template

Summary

  • Add a LubeLogger blueprint with the current upstream release image ghcr.io/hargata/lubelogger:v1.6.5.
  • Configure Dokploy routing on port 8080 plus domain, locale, and auth toggle environment variables.
  • Persist the official LubeLogger data and ASP.NET data-protection key directories, and register the template metadata/logo.

Refs #152.
/claim #152

Why this is low-risk

  • Only adds one new blueprint folder and one sorted meta.json entry.
  • No host port mappings, container_name, or explicit networks are introduced.
  • The compose service name matches the blueprint folder name.

Files changed

  • blueprints/lubelogger/docker-compose.yml - added: LubeLogger service, pinned image, env vars, persistent volumes, expose 8080.
  • blueprints/lubelogger/template.toml - added: Dokploy domain and environment configuration.
  • blueprints/lubelogger/lubelogger.png - added: Official upstream logo.
  • meta.json - modified: Adds the LubeLogger metadata entry.

Coverage

  • Template structure validates against the new blueprint folder.
  • Docker Compose structure validates for the LubeLogger compose file.
  • meta.json remains deduplicated, sorted, and schema-clean with 390 entries.
  • The pinned GHCR image tag v1.6.5 resolves successfully.
  • The preview app TypeScript project still compiles.

Verification

  • node dedupe-and-sort-meta.js - passed
  • cd build-scripts && npm run validate-template -- --dir ../blueprints/lubelogger - passed
  • cd build-scripts && npm run validate-docker-compose -- --file ../blueprints/lubelogger/docker-compose.yml - passed
  • node build-scripts/process-meta.js --verbose --output /tmp/dokploy-meta-test.json && diff -q meta.json /tmp/dokploy-meta-test.json - passed
  • LUBELOGGER_LOCALE=en_US.UTF-8 LUBELOGGER_DOMAIN=https://lubelogger.example.com LUBELOGGER_ENABLE_AUTH=false docker compose -f blueprints/lubelogger/docker-compose.yml config --quiet - passed
  • docker manifest inspect ghcr.io/hargata/lubelogger:v1.6.5 >/dev/null - passed
  • cd app && ./node_modules/.bin/tsc -b - passed

Reviewer notes

  • LubeLogger was absent from the existing blueprints and there were no open LubeLogger PRs when this was prepared.
  • The image tag matches upstream release v1.6.5 published 2026-05-16.

🔄 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/896 **Author:** [@100more](https://github.com/100more) **Created:** 5/21/2026 **Status:** 🔄 Open **Base:** `canary` ← **Head:** `codex/add-lubelogger-template` --- ### 📝 Commits (1) - [`dd79917`](https://github.com/Dokploy/templates/commit/dd79917e3a3928b8e54adf65a2e5a8254a51809b) feat: add LubeLogger template ### 📊 Changes **4 files changed** (+56 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/lubelogger/docker-compose.yml` (+20 -0) ➕ `blueprints/lubelogger/lubelogger.png` (+0 -0) ➕ `blueprints/lubelogger/template.toml` (+18 -0) 📝 `meta.json` (+18 -0) </details> ### 📄 Description # feat: add LubeLogger template ## Summary - Add a LubeLogger blueprint with the current upstream release image `ghcr.io/hargata/lubelogger:v1.6.5`. - Configure Dokploy routing on port 8080 plus domain, locale, and auth toggle environment variables. - Persist the official LubeLogger data and ASP.NET data-protection key directories, and register the template metadata/logo. Refs #152. /claim #152 ## Why this is low-risk - Only adds one new blueprint folder and one sorted `meta.json` entry. - No host port mappings, `container_name`, or explicit networks are introduced. - The compose service name matches the blueprint folder name. ## Files changed - `blueprints/lubelogger/docker-compose.yml` - added: LubeLogger service, pinned image, env vars, persistent volumes, expose 8080. - `blueprints/lubelogger/template.toml` - added: Dokploy domain and environment configuration. - `blueprints/lubelogger/lubelogger.png` - added: Official upstream logo. - `meta.json` - modified: Adds the LubeLogger metadata entry. ## Coverage - Template structure validates against the new blueprint folder. - Docker Compose structure validates for the LubeLogger compose file. - `meta.json` remains deduplicated, sorted, and schema-clean with 390 entries. - The pinned GHCR image tag `v1.6.5` resolves successfully. - The preview app TypeScript project still compiles. ## Verification - `node dedupe-and-sort-meta.js` - passed - `cd build-scripts && npm run validate-template -- --dir ../blueprints/lubelogger` - passed - `cd build-scripts && npm run validate-docker-compose -- --file ../blueprints/lubelogger/docker-compose.yml` - passed - `node build-scripts/process-meta.js --verbose --output /tmp/dokploy-meta-test.json && diff -q meta.json /tmp/dokploy-meta-test.json` - passed - `LUBELOGGER_LOCALE=en_US.UTF-8 LUBELOGGER_DOMAIN=https://lubelogger.example.com LUBELOGGER_ENABLE_AUTH=false docker compose -f blueprints/lubelogger/docker-compose.yml config --quiet` - passed - `docker manifest inspect ghcr.io/hargata/lubelogger:v1.6.5 >/dev/null` - passed - `cd app && ./node_modules/.bin/tsc -b` - passed ## Reviewer notes - LubeLogger was absent from the existing blueprints and there were no open LubeLogger PRs when this was prepared. - The image tag matches upstream release `v1.6.5` published 2026-05-16. --- <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-06-17 06:29:36 -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#14313
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?