Deploy Byparr on tools-pve
This commit is contained in:
@@ -0,0 +1,23 @@
|
||||
# Byparr
|
||||
|
||||
Private LAN browser-fetch service on `tools-pve` for pages that reject ordinary
|
||||
HTTP clients.
|
||||
|
||||
- API docs: `http://192.168.50.49:8191/docs`
|
||||
- FlareSolverr-compatible endpoint: `POST http://192.168.50.49:8191/v1`
|
||||
- Authentication: none; the port is bound only to the host LAN address
|
||||
- Persistent state: none
|
||||
|
||||
Example:
|
||||
|
||||
```bash
|
||||
curl -sS http://192.168.50.49:8191/v1 \
|
||||
-H 'Content-Type: application/json' \
|
||||
-d '{"cmd":"request.get","url":"https://example.com","maxTimeout":120000}'
|
||||
```
|
||||
|
||||
The upstream image is pinned to an immutable `linux/amd64` digest. Browser
|
||||
scratch data and cache are RAM-backed because Byparr performs frequent writes.
|
||||
The local TCP healthcheck deliberately avoids Byparr's `/health` endpoint,
|
||||
which opens an external page on every check.
|
||||
|
||||
Reference in New Issue
Block a user