A docker-based warehouse of Selenium servers running chrome and firefox, ready to be checked out for use by Selenium WebDriver clients.

Configuration is done entirely with environment variables (detailed below), which should make it trivial to use something other than systemd to manage the wharf service, should systemd be unavailable.

[Unit]
Description=WebDriver Wharf
After=docker.service

[Service]
Type=simple
ExecStart=/usr/bin/webdriver-wharf
EnvironmentFile=/etc/default/webdriver-wharf

[Install]
WantedBy=multi-user.target

Note that on RPM-bases systems, EnvironmentFile should probably be /etc/sysconfig/webdriver-wharf

The name of the docker image to spawn in the wharf pool.

Defaults to cfmeqe/sel_ff_chrome, but can be any docker image that exposes a selenium server on port 4444 and a VNC server on port 5999 (display :99). The sel_ff_chrome image also exposes nginx's json-based file browser on port 80.

Number of containers to keep in the active pool, ready for checkout.

Defaults to 4

Maximum time, in seconds, a container can be checked out before it is reaped.

Defaults to 3600, set to 0 for no max checkout time (probably a bad idea)

Interval, in seconds, of how often wharf will check for updates to the docker image.

Defaults to one hour (3600 seconds)

Interval, in seconds, of how often wharf will rebalance the active container pool.

Frequent rebalancing should not be necessary, and indicates a wharf bug.

Defaults to six hours (21600 seconds)

Loglevel for wharf's console spam. Must be one of python's builtin loglevels: 'DEBUG', 'INFO', 'WARNING', 'ERROR', 'CRITICAL'

Defaults to 'INFO', which offers a running commentary on the starting, stopping, and destruction of containers

Host address to bind to.

Defaults to 0.0.0.0 (all interfaces)

Host port (TCP) to bind to.

Defaults to 4899

How long, in seconds, wharf will wait when starting a container before deciding the container has failed to start.

Defaults to 60

Database URL that wharf should connect to for container tracking.

By default, wharf creates and maintains its own SQLite database in sane locations, though not necessarily the "correct" one according to the Filesystem Hierarchy Standard

If set, this value is passed directly to sqlalchemy with no further processing. See the sqlalchemy docs for information regarding the construction of URLs. When using other database engines, wharf takes no responsibility for installing the correct driver, needs the ability to create tables, and most importantly has not been tested with that engine.