Originally created by @OJ7 on GitHub (Mar 6, 2025).
Coming from Nginx Proxy Manager, I'm able to disable/enable routes whenever I want. Is there an equivalent to disable resources in Pangolin?
Originally created by @OJ7 on GitHub (Mar 6, 2025).
Coming from Nginx Proxy Manager, I'm able to disable/enable routes whenever I want. Is there an equivalent to disable resources in Pangolin?
I just found an option to disable a local target under the resource's Connectivity. This results in a no available server message when navigating to that host (which is slightly different from navigating to a non-existent host which gives an error like DNS address could not be found). I think it works for me, but will leave this issue open in case there's interest in adding it to the Resource level instead of the Target level to get the latter behavior.
@OJ7 commented on GitHub (Mar 6, 2025):
I just found an option to disable a local target under the resource's Connectivity. This results in a `no available server` message when navigating to that host (which is slightly different from navigating to a non-existent host which gives an error like `DNS address could not be found`). I think it works for me, but will leave this issue open in case there's interest in adding it to the Resource level instead of the Target level to get the latter behavior.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @OJ7 on GitHub (Mar 6, 2025).
Coming from Nginx Proxy Manager, I'm able to disable/enable routes whenever I want. Is there an equivalent to disable resources in Pangolin?
@OJ7 commented on GitHub (Mar 6, 2025):
I just found an option to disable a local target under the resource's Connectivity. This results in a
no available servermessage when navigating to that host (which is slightly different from navigating to a non-existent host which gives an error likeDNS address could not be found). I think it works for me, but will leave this issue open in case there's interest in adding it to the Resource level instead of the Target level to get the latter behavior.