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 #574] [MERGED] fix(habitica): add user to mongodb replicaset to enable Dokploy DB backups #12210

New Issue
Closed
opened 2026-06-13 14:03:36 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-06-13 14:03:36 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/574
Author: @jorgegomzar
Created: 12/7/2025
Status: ✅ Merged
Merged: 2/15/2026
Merged by: @Siumauricio

Base: canary ← Head: fix/habitica-security

📝 Commits (7)

  • 000c6fd fix: use environment variables from configuration in habitica-server
  • 12bf4a0 feat: add users to mongodb replicaSet
  • 1f5878c chore: less retries
  • 81d2863 chore: do not start server until mongo is healthy
  • 5a99b1d fix: ensure habitica user exists for habitica db
  • c079a72 fix: remove BASE_URL to prevent infinite redirects
  • f74670a fix: add missing ADMIN_EMAIL

📊 Changes

2 files changed (+82 additions, -17 deletions)

View changed files

📝 blueprints/habitica/docker-compose.yml (+66 -9)
📝 blueprints/habitica/template.toml (+16 -8)

📄 Description

What is this PR about?

Updates existing Habitica deployment to add user authentication via admin + habitica users on the MongoDB replicaSet via keyfile.

My main motivation was that I wanted to add DB backups, and Dokploy requires 1 user for this functionality to work.

Checklist

Before submitting this PR, please make sure that:

  • I have read the suggestions in the README.md file
  • I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.

🔄 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/574 **Author:** [@jorgegomzar](https://github.com/jorgegomzar) **Created:** 12/7/2025 **Status:** ✅ Merged **Merged:** 2/15/2026 **Merged by:** [@Siumauricio](https://github.com/Siumauricio) **Base:** `canary` ← **Head:** `fix/habitica-security` --- ### 📝 Commits (7) - [`000c6fd`](https://github.com/Dokploy/templates/commit/000c6fd92fecfd5b9a793fae3b6d813ee0f65e2d) fix: use environment variables from configuration in habitica-server - [`12bf4a0`](https://github.com/Dokploy/templates/commit/12bf4a0b064d9a7c23cf19831a615c4171c137c3) feat: add users to mongodb replicaSet - [`1f5878c`](https://github.com/Dokploy/templates/commit/1f5878c5bd723340f495c83effa10c1aecff76ec) chore: less retries - [`81d2863`](https://github.com/Dokploy/templates/commit/81d28630d4636e6ccad2c6ba2e122856e98267ee) chore: do not start server until mongo is healthy - [`5a99b1d`](https://github.com/Dokploy/templates/commit/5a99b1d935a60891b06fe7da335de35d90008e0f) fix: ensure habitica user exists for habitica db - [`c079a72`](https://github.com/Dokploy/templates/commit/c079a72334d32dee463701012f1449d65d65c61f) fix: remove BASE_URL to prevent infinite redirects - [`f74670a`](https://github.com/Dokploy/templates/commit/f74670a8ef078c8c8fd9b3e3a40acfd27afb0f99) fix: add missing ADMIN_EMAIL ### 📊 Changes **2 files changed** (+82 additions, -17 deletions) <details> <summary>View changed files</summary> 📝 `blueprints/habitica/docker-compose.yml` (+66 -9) 📝 `blueprints/habitica/template.toml` (+16 -8) </details> ### 📄 Description # What is this PR about? Updates existing Habitica deployment to add user authentication via admin + habitica users on the MongoDB replicaSet via keyfile. My main motivation was that I wanted to add DB backups, and Dokploy requires 1 user for this functionality to work. # 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-suggestions-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. --- <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-13 14:03: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#12210
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?