github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-07-16 22:55:14 -05:00
Code Issues 1.6k Packages Projects Releases 79 Wiki Activity

[GH-ISSUE #815] Feature Request: Managing Domains in UI #8412

New Issue
Closed
opened 2026-04-30 04:12:51 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-30 04:12:51 -05:00
Owner
Copy Link

Originally created by @kalikid021 on GitHub (May 31, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/815

From what I can see, adding an additional domain to Pangolin, requires editing the config.yml however after making that change, I cannot just re-run docker compose up -d and have the stack pickup the new domain in the config. I have to bring down the full stack with docker compose down and then bring the stack back up in order for the config change to take effect.

This creates issues and inconsistencies when running services through Pangolin. This wouldn't be considered a "mission critical" capable application, if the application needs to be taken offline each time a configuration change needs to be made.

I imagine this has more to do with Traefik than pangolin, but being able to make changes to the domain structure seems like a core component of the application, and managing those changes in the UI, and having Traefik reload the config upon clicking save in the Pangolin UI, would be ideal as opposed to the current process. Also managing Traefik from the Pangolin UI (as it's also a core component) would be an ideal addition as well.

Hopefully this gets put on the roadmap. I really like the software, and it is very promising. I'm looking forward to replacing CF Tunnels with it, and have been slowly integrating it into my secondary home lab services. I'm not ready to move things like IDP/Auth over yet due to the feature request. I am looking forward to it's continued progress and development.

Originally created by @kalikid021 on GitHub (May 31, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/815 From what I can see, adding an additional domain to Pangolin, requires editing the config.yml however after making that change, I cannot just re-run `docker compose up -d` and have the stack pickup the new domain in the config. I have to bring down the full stack with `docker compose down` and then bring the stack back up in order for the config change to take effect. This creates issues and inconsistencies when running services through Pangolin. This wouldn't be considered a "mission critical" capable application, if the application needs to be taken offline each time a configuration change needs to be made. I imagine this has more to do with Traefik than pangolin, but being able to make changes to the domain structure seems like a core component of the application, and managing those changes in the UI, and having Traefik reload the config upon clicking save in the Pangolin UI, would be ideal as opposed to the current process. Also managing Traefik from the Pangolin UI (as it's also a core component) would be an ideal addition as well. Hopefully this gets put on the roadmap. I really like the software, and it is very promising. I'm looking forward to replacing CF Tunnels with it, and have been slowly integrating it into my secondary home lab services. I'm not ready to move things like IDP/Auth over yet due to the feature request. I am looking forward to it's continued progress and development.
GiteaMirror commented 2026-04-30 04:12:52 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Jun 1, 2025):

Hi! Thanks for the suggestion! I think this is a duplicate of https://github.com/orgs/fosrl/discussions/251 so I am going to close but feel free to reopen if there is something I missed.

<!-- gh-comment-id:2927388288 --> @oschwartz10612 commented on GitHub (Jun 1, 2025): Hi! Thanks for the suggestion! I think this is a duplicate of https://github.com/orgs/fosrl/discussions/251 so I am going to close but feel free to reopen if there is something I missed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
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/pangolin#8412
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?