Now that Newt has access to the Docker socket, would it make sense to explore support for starting and stopping containers dynamically based on usage patterns?
For example, some services are only needed sporadically and could be started when a request is received and stopped afterwards. This could help reduce resource usage for less frequently accessed containers.
Would this be within the scope of Pangolin? I know some solutions for caddy and other reverse proxies exist, but it may be cool to integrate it within pangolin ecosystem.
Originally created by @MyWay on GitHub (Jun 12, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/901
Now that Newt has access to the Docker socket, would it make sense to explore support for starting and stopping containers dynamically based on usage patterns?
For example, some services are only needed sporadically and could be started when a request is received and stopped afterwards. This could help reduce resource usage for less frequently accessed containers.
Would this be within the scope of Pangolin? I know some solutions for caddy and other reverse proxies exist, but it may be cool to integrate it within pangolin ecosystem.
@oschwartz10612 commented on GitHub (Jun 13, 2025):
This is a very interesting idea thanks for posting! We very well could do this but it might not happen super soon unless there is much support. I am going to move this to a feature discussion so people can upvote though!
This could be good in situations where you pay for compute or can pay for less compute only when it is needed.
<!-- gh-comment-id:2970395772 -->
@oschwartz10612 commented on GitHub (Jun 13, 2025):
This is a very interesting idea thanks for posting! We very well could do this but it might not happen super soon unless there is much support. I am going to move this to a feature discussion so people can upvote though!
This could be good in situations where you pay for compute or can pay for less compute only when it is needed.
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 @MyWay on GitHub (Jun 12, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/901
Now that Newt has access to the Docker socket, would it make sense to explore support for starting and stopping containers dynamically based on usage patterns?
For example, some services are only needed sporadically and could be started when a request is received and stopped afterwards. This could help reduce resource usage for less frequently accessed containers.
Would this be within the scope of Pangolin? I know some solutions for caddy and other reverse proxies exist, but it may be cool to integrate it within pangolin ecosystem.
@oschwartz10612 commented on GitHub (Jun 13, 2025):
This is a very interesting idea thanks for posting! We very well could do this but it might not happen super soon unless there is much support. I am going to move this to a feature discussion so people can upvote though!
This could be good in situations where you pay for compute or can pay for less compute only when it is needed.