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

[PR #654] [CLOSED] Add LinknLink Template with Docker Compose and Metadata #1985

New Issue
Closed
opened 2026-04-20 11:01:23 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 11:01:23 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/654
Author: @sonmezerekrem
Created: 1/15/2026
Status: ❌ Closed

Base: canary ← Head: add-linknlink-template

📝 Commits (1)

  • 201e76a feat: add LinknLink template with Docker Compose and metadata

📊 Changes

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

View changed files

➕ blueprints/linknlink/docker-compose.yml (+42 -0)
➕ blueprints/linknlink/linknlink.svg (+4 -0)
➕ blueprints/linknlink/template.toml (+24 -0)
📝 meta.json (+18 -0)

📄 Description

  • Introduced LinknLink, a link management application, with a comprehensive Docker Compose setup for both backend and frontend services.
  • Added metadata in meta.json including description, logo, and relevant links.
  • Created template.toml for environment variable configuration and service deployment.

What is this PR about?

New PR of LinknLink

Checklist

Before submitting this PR, please make sure that:

Issues related (if applicable)

Close automatically the related issues using the keywords: closes #ISSUE_NUMBER

Screenshots or Videos

https://github.com/sonmezerekrem/linknlink

Greptile Summary

Added a new LinknLink template for a self-hosted link management application. The template includes a two-service architecture with PocketBase backend and Next.js frontend, both using container images from the author's GitHub Container Registry. The docker-compose configuration follows Dokploy conventions by using expose instead of ports, avoiding container_name and networks, and including proper restart policies and volume mounts. The template.toml correctly configures domain routing to the frontend service and defines all necessary environment variables with appropriate Dokploy helpers (${domain}, ${email}, ${password:32}). The meta.json entry is properly structured with all required fields and positioned alphabetically between "linkding" and "linkstack" entries.

Confidence Score: 4/5

  • This PR is safe to merge with only minor considerations around external image dependencies
  • The template follows all Dokploy conventions correctly (no ports mapping, no container_name, no networks, proper restart policies). Environment variables are properly configured with security helpers. The main consideration is that the template uses custom Docker images from the author's GitHub Container Registry rather than official images, which means users are trusting the author's build process. However, this is a common pattern for new applications without official Docker images. All required files are present and correctly structured.
  • No files require special attention

Last reviewed commit: 201e76a

(2/5) Greptile learns from your feedback when you react with thumbs up/down!

Context used:

  • Context from dashboard - 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/654 **Author:** [@sonmezerekrem](https://github.com/sonmezerekrem) **Created:** 1/15/2026 **Status:** ❌ Closed **Base:** `canary` ← **Head:** `add-linknlink-template` --- ### 📝 Commits (1) - [`201e76a`](https://github.com/Dokploy/templates/commit/201e76a2d86b194aeada948179c574c1f7ca114d) feat: add LinknLink template with Docker Compose and metadata ### 📊 Changes **4 files changed** (+88 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/linknlink/docker-compose.yml` (+42 -0) ➕ `blueprints/linknlink/linknlink.svg` (+4 -0) ➕ `blueprints/linknlink/template.toml` (+24 -0) 📝 `meta.json` (+18 -0) </details> ### 📄 Description - Introduced LinknLink, a link management application, with a comprehensive Docker Compose setup for both backend and frontend services. - Added metadata in meta.json including description, logo, and relevant links. - Created template.toml for environment variable configuration and service deployment. ## What is this PR about? New PR of LinknLink ## Checklist Before submitting this PR, please make sure that: - [x] I have read the suggestions in the README.md file https://github.com/Dokploy/templates?tab=readme-ov-file#general-requirements-when-creating-a-template - [x] I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong. - [ ] I have added tests that demonstrate that my correction works or that my new feature works. ## Issues related (if applicable) Close automatically the related issues using the keywords: `closes #ISSUE_NUMBER` ## Screenshots or Videos https://github.com/sonmezerekrem/linknlink <!-- greptile_comment --> <h3>Greptile Summary</h3> Added a new LinknLink template for a self-hosted link management application. The template includes a two-service architecture with PocketBase backend and Next.js frontend, both using container images from the author's GitHub Container Registry. The docker-compose configuration follows Dokploy conventions by using `expose` instead of `ports`, avoiding `container_name` and `networks`, and including proper restart policies and volume mounts. The template.toml correctly configures domain routing to the frontend service and defines all necessary environment variables with appropriate Dokploy helpers (`${domain}`, `${email}`, `${password:32}`). The meta.json entry is properly structured with all required fields and positioned alphabetically between "linkding" and "linkstack" entries. <h3>Confidence Score: 4/5</h3> - This PR is safe to merge with only minor considerations around external image dependencies - The template follows all Dokploy conventions correctly (no ports mapping, no container_name, no networks, proper restart policies). Environment variables are properly configured with security helpers. The main consideration is that the template uses custom Docker images from the author's GitHub Container Registry rather than official images, which means users are trusting the author's build process. However, this is a common pattern for new applications without official Docker images. All required files are present and correctly structured. - No files require special attention <sub>Last reviewed commit: 201e76a</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>
GiteaMirror added the pull-request label 2026-04-20 11:01: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#1985
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?