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 #932] [MERGED] feat: add FileRun template #17263

New Issue
Closed
opened 2026-07-16 06:28:39 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-07-16 06:28:39 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/932
Author: @rohitmulani63-ops
Created: 6/22/2026
Status: ✅ Merged
Merged: 7/8/2026
Merged by: @Siumauricio

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

📝 Commits (6)

  • 7d30281 feat: add FileRun template
  • a185fe8 fix: remove FileRun template BOM
  • dabe846 Align FileRun compose with upstream runtime settings
  • 16d3529 Merge remote-tracking branch 'origin/canary' into codex/add-filerun-template
  • 3e856b0 Merge remote-tracking branch 'origin/canary' into codex/add-filerun-template
  • 88fae2f fix: chown named volumes so the non-root filerun user can install on first run

📊 Changes

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

View changed files

➕ blueprints/filerun/docker-compose.yml (+44 -0)
➕ blueprints/filerun/filerun.svg (+7 -0)
➕ blueprints/filerun/meta.json (+17 -0)
➕ blueprints/filerun/template.toml (+19 -0)

📄 Description

What is this PR about?

Adds a FileRun template for Dokploy based on the official FileRun Docker installation guide.

This template includes:

  • FileRun web service using the official FileRun container
  • MariaDB 12.2 database service
  • generated database credentials through Dokploy template variables
  • persistent volumes for FileRun app files, user files, and MariaDB data
  • Dokploy domain routing on the FileRun service port

Notes

  • Direct host ports and legacy Docker links from the upstream example were intentionally omitted for Dokploy compatibility.
  • After first setup, FileRun's superuser home folder should be set to /user-files, matching the official Docker guidance.
  • Docker runtime testing was not possible in this environment because Docker is not installed, so I validated the template structure and compose syntax with the repository scripts.

/claim #152
Closes #94

Validation

  • node dedupe-and-sort-meta.js
  • npm run validate-template -- --dir ../blueprints/filerun
  • npm run validate-docker-compose -- --file ../blueprints/filerun/docker-compose.yml
  • git diff --check

Screenshots or Videos

Not applicable for this template-only change.

🔄 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/932 **Author:** [@rohitmulani63-ops](https://github.com/rohitmulani63-ops) **Created:** 6/22/2026 **Status:** ✅ Merged **Merged:** 7/8/2026 **Merged by:** [@Siumauricio](https://github.com/Siumauricio) **Base:** `canary` ← **Head:** `codex/add-filerun-template` --- ### 📝 Commits (6) - [`7d30281`](https://github.com/Dokploy/templates/commit/7d302816cdb382160aabfe3b2296a1cf565b9bba) feat: add FileRun template - [`a185fe8`](https://github.com/Dokploy/templates/commit/a185fe862558146ff2fab98e221cafb35b9ef80a) fix: remove FileRun template BOM - [`dabe846`](https://github.com/Dokploy/templates/commit/dabe8466acf6f0efdbe3ef8c70fae9957d53d3ab) Align FileRun compose with upstream runtime settings - [`16d3529`](https://github.com/Dokploy/templates/commit/16d35299a740f3618ac6c25fb2567d828e68ef4b) Merge remote-tracking branch 'origin/canary' into codex/add-filerun-template - [`3e856b0`](https://github.com/Dokploy/templates/commit/3e856b0316506b83b590d4ac7c79cb2aeba87e76) Merge remote-tracking branch 'origin/canary' into codex/add-filerun-template - [`88fae2f`](https://github.com/Dokploy/templates/commit/88fae2f9ccf1ee3cff86404f5bf23554eb4161fb) fix: chown named volumes so the non-root filerun user can install on first run ### 📊 Changes **4 files changed** (+87 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/filerun/docker-compose.yml` (+44 -0) ➕ `blueprints/filerun/filerun.svg` (+7 -0) ➕ `blueprints/filerun/meta.json` (+17 -0) ➕ `blueprints/filerun/template.toml` (+19 -0) </details> ### 📄 Description ## What is this PR about? Adds a FileRun template for Dokploy based on the official FileRun Docker installation guide. This template includes: - FileRun web service using the official FileRun container - MariaDB 12.2 database service - generated database credentials through Dokploy template variables - persistent volumes for FileRun app files, user files, and MariaDB data - Dokploy domain routing on the FileRun service port ## Notes - Direct host ports and legacy Docker links from the upstream example were intentionally omitted for Dokploy compatibility. - After first setup, FileRun's superuser home folder should be set to `/user-files`, matching the official Docker guidance. - Docker runtime testing was not possible in this environment because Docker is not installed, so I validated the template structure and compose syntax with the repository scripts. /claim #152 Closes #94 ## Validation - `node dedupe-and-sort-meta.js` - `npm run validate-template -- --dir ../blueprints/filerun` - `npm run validate-docker-compose -- --file ../blueprints/filerun/docker-compose.yml` - `git diff --check` ## Screenshots or Videos Not applicable for this template-only change. --- <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-16 06:28:39 -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#17263
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?