chrome

Chrome instance and panel to manage startup and shutdowns easily.

Usage

1. Can spawn and shutdown multiple chrome instances.
2. Get chrome ws connections and status.

The current instance binds chrome to 0.0.0.0 when starting via API.

Use the env variable REMOTE_ADDRESS to change the address of the chrome instance between physical or network.

The application will pass alp health checks when using port 6000 to get the status of the chrome container.

A side loaded application is required to run chrome on a load balancer, one of the main purposes of the control panel.

The default port is 9222 for chrome.

Building without Docker

In order to build without docker set the BUILD_CHROME env var to true.

Mac

If your running locally use the following to start the args with the first param chrome_driver '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome'

API

1. POST: fork to start a new chrome instance or use fork/$port with the port to startup the instance.
2. POST: shutdown/$PID to shutdown the instance. ex: curl --location --request POST 'http://localhost:6000/shutdown/77057'

Args

1. The first arg is the chrome application location.
2. The second arg is the chrome address 127.0.0.1.
3. The third arg you can pass in init to auto start chrome on 9222.

Example to start chrome (all params are optional):

```sh chrome_driver '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome' 127.0.0.1 init

Chrome PID: 87659

Chrome server at localhost:6000

DevTools listening on ws://127.0.0.1:9222/devtools/browser/c789f9e0-7f65-495d-baee-243eb454ea15

```