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

[PR #933] [MERGED] feat: add Rallly template #15263

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

📋 Pull Request Information

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

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

📝 Commits (1)

  • 5db8f49 feat: add Rallly template

📊 Changes

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

View changed files

➕ blueprints/rallly/docker-compose.yml (+66 -0)
➕ blueprints/rallly/rallly.svg (+8 -0)
➕ blueprints/rallly/template.toml (+40 -0)
📝 meta.json (+17 -0)

📄 Description

What is this PR about?

Adds a Rallly template for Dokploy using the current self-hosted Rallly image and a Dokploy-friendly service layout.

This template includes:

  • Rallly web app pinned to lukevella/rallly:4.11.1
  • PostgreSQL database with persistent storage
  • S3-compatible MinIO storage with a bucket initialization helper
  • generated secrets for database, session secret, and object storage
  • explicit SMTP variables because Rallly self-hosting requires transactional email for production use
  • Dokploy domain routing directly to the Rallly service on port 3000

Why this shape

The official Rallly self-hosted stack includes Traefik and host port bindings. For Dokploy, this PR intentionally removes the bundled proxy/host-port layer and lets Dokploy own routing through the template domain configuration.

/claim #152
Closes #121

Validation

  • node dedupe-and-sort-meta.js
  • npm run validate-template -- --dir ../blueprints/rallly
  • npm run validate-docker-compose -- --file ../blueprints/rallly/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/933 **Author:** [@rohitmulani63-ops](https://github.com/rohitmulani63-ops) **Created:** 6/22/2026 **Status:** ✅ Merged **Merged:** 7/7/2026 **Merged by:** [@Siumauricio](https://github.com/Siumauricio) **Base:** `canary` ← **Head:** `codex/add-rallly-template` --- ### 📝 Commits (1) - [`5db8f49`](https://github.com/Dokploy/templates/commit/5db8f49ef3ff0b1c1b6454d8669d4a3e1c5800fa) feat: add Rallly template ### 📊 Changes **4 files changed** (+131 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/rallly/docker-compose.yml` (+66 -0) ➕ `blueprints/rallly/rallly.svg` (+8 -0) ➕ `blueprints/rallly/template.toml` (+40 -0) 📝 `meta.json` (+17 -0) </details> ### 📄 Description ## What is this PR about? Adds a Rallly template for Dokploy using the current self-hosted Rallly image and a Dokploy-friendly service layout. This template includes: - Rallly web app pinned to `lukevella/rallly:4.11.1` - PostgreSQL database with persistent storage - S3-compatible MinIO storage with a bucket initialization helper - generated secrets for database, session secret, and object storage - explicit SMTP variables because Rallly self-hosting requires transactional email for production use - Dokploy domain routing directly to the Rallly service on port 3000 ## Why this shape The official Rallly self-hosted stack includes Traefik and host port bindings. For Dokploy, this PR intentionally removes the bundled proxy/host-port layer and lets Dokploy own routing through the template domain configuration. /claim #152 Closes #121 ## Validation - `node dedupe-and-sort-meta.js` - `npm run validate-template -- --dir ../blueprints/rallly` - `npm run validate-docker-compose -- --file ../blueprints/rallly/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-13 16:58:34 -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#15263
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?