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_PORT3000  
CFG_BROWSERLESS_TOKEN""  
CFG_BROWSERLESS_TIMEOUT30000  
CFG_BROWSERLESS_CONCURRENCY10  
CFG_BROWSERLESS_PREBOOTfalse  
CFG_BROWSERLESS_KEEPALIVEfalse  
CFG_BROWSERLESS_QUEUE10  
CFG_BROWSERLESS_REFRESH1800000  
CFG_BROWSERLESS_MAXMEM99  
CFG_BROWSERLESS_MAXCPU99  

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

 

Tags:
Created by Robert Pele on 2021/05/06 09:09

Navigation