[GH-ISSUE #24] [Feature Request] Support for multiple proxy pools and ports in a single instance #13

New issue

Open

opened 2026-03-01 14:35:57 +03:00 by kerem · 0 comments

kerem commented

2026-03-01 14:35:57 +03:00

Owner

Originally created by @yudinikita on GitHub (Feb 15, 2026).
Original GitHub issue: https://github.com/alpkeskin/rota/issues/24

Currently, rota supports a single proxy pool and one listening port per instance. To use different proxy sets for different applications (e.g., Application A needs residential proxies, while Application B needs datacenter ones), users must deploy multiple separate instances or Docker containers.

Proposed Solution

Add the ability to define multiple "pools" within the configuration file. Each pool should be able to:

Listen on a specific port.
Use a specific proxy source file/list.
Have its own rotation strategy

Example configuration concept:

pools:
  - name: "app_one_pool"
    port: 8001
    source: "./proxies_fast.txt"
    strategy: "round-robin"
  
  - name: "app_two_pool"
    port: 8002
    source: "./proxies_cheap.txt"
    strategy: "random"

Why this is needed?

Running a single Go binary is more efficient than managing dozens of separate containers for large-scale setups.
It allows users to separate traffic for different target websites with different rate limits.
Managing one configuration file is easier than maintaining multiple deployment scripts.

This feature would make rota much more powerful for developers who need to manage complex scraping infrastructures.

Originally created by @yudinikita on GitHub (Feb 15, 2026). Original GitHub issue: https://github.com/alpkeskin/rota/issues/24 Currently, rota supports a single proxy pool and one listening port per instance. To use different proxy sets for different applications (e.g., Application A needs residential proxies, while Application B needs datacenter ones), users must deploy multiple separate instances or Docker containers. ### Proposed Solution Add the ability to define multiple "pools" within the configuration file. Each pool should be able to: 1. Listen on a specific port. 2. Use a specific proxy source file/list. 3. Have its own rotation strategy **Example configuration concept:** ```yaml pools: - name: "app_one_pool" port: 8001 source: "./proxies_fast.txt" strategy: "round-robin" - name: "app_two_pool" port: 8002 source: "./proxies_cheap.txt" strategy: "random" ``` ### Why this is needed? - Running a single Go binary is more efficient than managing dozens of separate containers for large-scale setups. - It allows users to separate traffic for different target websites with different rate limits. - Managing one configuration file is easier than maintaining multiple deployment scripts. This feature would make rota much more powerful for developers who need to manage complex scraping infrastructures.