github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-03-12 10:05:25 -05:00
Code Issues 155 Packages Projects Releases Wiki Activity

[PR #496] [MERGED] fix(rybbit): add DOMAIN_NAME env var to resolve Invalid Origin issue #499

New Issue
Closed
opened 2025-11-22 20:39:50 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-22 20:39:50 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/496
Author: @shadyar-bakr
Created: 11/1/2025
Status: ✅ Merged
Merged: 11/8/2025
Merged by: @Siumauricio

Base: main ← Head: fix/rybbit-template

📝 Commits (2)

  • 9e34a71 Update docker-compose.yml to include DOMAIN_NAME variable
  • ef7b1e1 Add DOMAIN_NAME to template

📊 Changes

2 files changed (+5 additions, -2 deletions)

View changed files

📝 blueprints/rybbit/docker-compose.yml (+4 -2)
📝 blueprints/rybbit/template.toml (+1 -0)

📄 Description

This PR adds the missing DOMAIN_NAME environment variable to the Rybbit template and updates comments to clarify how BASE_URL and DOMAIN_NAME should be configured.
Without this variable, authentication and organization creation failed due to an Invalid Origin error when validating requests against the deployed domain.

Files Updated

  • blueprints/rybbit/docker-compose.yml

    • Added DOMAIN_NAME=${DOMAIN_NAME} to both backend and frontend environment sections.
    • Updated the comment above the domain configuration to mention both BASE_URL and DOMAIN_NAME.

  • blueprints/rybbit/template.toml

    • Added DOMAIN_NAME="${main_domain}" under [config.env] to ensure proper domain propagation in deployments.

Related Issues
Closes https://github.com/Dokploy/templates/issues/495, https://github.com/Dokploy/templates/issues/154, https://github.com/rybbit-io/rybbit/issues/413

Note: we can also update the template to rybbit latest, I have it running now, with no issues

🔄 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/496 **Author:** [@shadyar-bakr](https://github.com/shadyar-bakr) **Created:** 11/1/2025 **Status:** ✅ Merged **Merged:** 11/8/2025 **Merged by:** [@Siumauricio](https://github.com/Siumauricio) **Base:** `main` ← **Head:** `fix/rybbit-template` --- ### 📝 Commits (2) - [`9e34a71`](https://github.com/Dokploy/templates/commit/9e34a71b79a090550e1fa9e665368be96b6ae328) Update docker-compose.yml to include DOMAIN_NAME variable - [`ef7b1e1`](https://github.com/Dokploy/templates/commit/ef7b1e1db3fe592893d3324b9f58d6c8397aed87) Add DOMAIN_NAME to template ### 📊 Changes **2 files changed** (+5 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `blueprints/rybbit/docker-compose.yml` (+4 -2) 📝 `blueprints/rybbit/template.toml` (+1 -0) </details> ### 📄 Description This PR adds the missing `DOMAIN_NAME` environment variable to the Rybbit template and updates comments to clarify how `BASE_URL` and `DOMAIN_NAME` should be configured. Without this variable, authentication and organization creation failed due to an `Invalid Origin` error when validating requests against the deployed domain. Files Updated - `blueprints/rybbit/docker-compose.yml` - Added DOMAIN_NAME=${DOMAIN_NAME} to both backend and frontend environment sections. - Updated the comment above the domain configuration to mention both BASE_URL and DOMAIN_NAME. - `blueprints/rybbit/template.toml` - Added `DOMAIN_NAME="${main_domain}"` under `[config.env]` to ensure proper domain propagation in deployments. Related Issues Closes https://github.com/Dokploy/templates/issues/495, https://github.com/Dokploy/templates/issues/154, https://github.com/rybbit-io/rybbit/issues/413 _Note_: we can also update the template to rybbit latest, I have it running now, with no issues --- <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 2025-11-22 20:39:50 -06: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#499
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?