RPE-Browserless
Last modified by Christian Reiber on 2021/09/24 19:23
Purpose
This software stack provides Browserless, a "Google Chrome as a Service". It allows for remote clients to connect, drive, and execute Google Chrome headless. It offers first-class integrations with the Puppeteer and Selenium Webdriver APIs.
Properties
Stack-Description | Remote Processing Engine (RPE), Browserless/Chrome Web Rendering |
---|---|
Stack-Image | docker.msg.team/ps/docker-stack-rpe-browserless |
Stack-Version | 1.50.0 |
Stack-Release | 20220110 |
Product-Name | Browserless & Chrome |
Product-Vendor | Browserless Development Team & Google, Inc. |
Product-Contact | https://browserless.io/ |
Product-Model | Open Source |
Product-License | GPL |
Product-Limits | none |
Implementation Base | Node.js |
Execution Base | <application server> |
Initial Start Time | 00:00:58 |
Documentation | https://docs.browserless.io/docs/puppeteer-library.html |
Topology
The stack consists of 1 container:
- rpe-browserless: bar
Configuration
Variable Name | Default | Meaning | |
CFG_BROWSERLESS_PORT | 3000 | ||
CFG_BROWSERLESS_TOKEN | "" | ||
CFG_BROWSERLESS_TIMEOUT | 30000 | ||
CFG_BROWSERLESS_CONCURRENCY | 10 | ||
CFG_BROWSERLESS_PREBOOT | false | ||
CFG_BROWSERLESS_KEEPALIVE | false | ||
CFG_BROWSERLESS_QUEUE | 10 | ||
CFG_BROWSERLESS_REFRESH | 1800000 | ||
CFG_BROWSERLESS_MAXMEM | 99 | ||
CFG_BROWSERLESS_MAXCPU | 99 |
See also the variables which control integration of the stack into the reverse proxy.
For changes to take effect the stack has to be reinstalled.
First Steps
Please check the Puppeteer Docu
Administration Commands
Related Documents