Skip to content

Add NodeMaven provider - #6

Open
alkaz-nodemaven wants to merge 1 commit into
davidteather:mainfrom
alkaz-nodemaven:feat/nodemaven-provider
Open

alkaz-nodemaven wants to merge 1 commit into
davidteather:mainfrom
alkaz-nodemaven:feat/nodemaven-provider

Conversation

@alkaz-nodemaven

Copy link
Copy Markdown

Adds a NodeMaven provider, following the "Adding a New Proxy Provider" guide.

NodeMaven is one gateway where the username selects the exit, so there is no API call: the provider builds sessions proxies, each with its own sticky session id (-sid-<hex>, one exit IP each). Targeting goes in username_suffix (e.g. "-country-us"), session lifetime in ttl, and sessions=0 returns one rotating proxy. HTTP on 8080, SOCKS5 on 1080. Every refresh draws new session ids, so the docstring points to refresh_interval=0 for keeping the same exits.

  • proxyproviders/providers/nodemaven.py, exported from proxyproviders/__init__.py
  • Sphinx page and an entry in the supported providers list
  • unit tests (100% coverage of the new module, 99% overall) and an integration test that runs only with RUN_INTEGRATION_TESTS, NODEMAVEN_USERNAME and NODEMAVEN_PASSWORD set

Tests: unit suite 80 passed; black, isort, flake8 and mypy are clean.

NodeMaven is one gateway where the username selects the exit, so the
provider builds proxies instead of fetching a list: one sticky session id
per proxy, optional targeting through username_suffix and a session ttl,
HTTP on 8080 or SOCKS5 on 1080. Includes a docs page, unit tests and an
opt-in integration test.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant