This buildpack downloads and installs (headless) Google Chrome from your choice of release channels. It also installs chromedriver.
Installation is performed in the /layers directory in the image so you can mount your rails app overtop of /workspace for development.
You can choose your release channel by specifying GOOGLE_CHROME_CHANNEL as
a config var for your app, in your app.json (for Heroku CI and Review Apps),
or in your pipeline settings (for Heroku CI).
Valid values are stable, beta, and unstable. If unspecified, the stable
channel will be used.
This buildpack installs shims that always add --headless, --disable-gpu,
--no-sandbox, and --remote-debugging-port=9222 to any google-chrome
command as you'll have trouble running Chrome on a Heroku dyno otherwise.
You'll have two of these shims on your path: google-chrome and
google-chrome-$GOOGLE_CHROME_CHANNEL. They both point to the binary of
the selected channel.
To use Selenium with this buildpack, you'll also need Chrome's webdriver. This buildpack includes it.
Additionally, chromedriver expects Chrome to be installed at /usr/bin/google-chrome,
but that's a read-only filesystem in a Heroku slug. You'll need to tell Selenium/chromedriver
that the chrome binary is at $GOOGLE_CHROME_SHIM instead.
To make that easier, this buildpack makes $GOOGLE_CHROME_BIN, and
$GOOGLE_CHROME_SHIM available as environment variables. With them, you can
use the standard location locally and the custom location on Heroku. An example
configuration for Ruby's Capybara:
chrome_bin = ENV.fetch('GOOGLE_CHROME_BIN', nil)
Capybara.register_driver :chrome do |app|
options = Selenium::WebDriver::Chrome::Options.new
options.binary = chrome_bin if chrome_bin
Capybara::Selenium::Driver.new(
app,
browser: :chrome,
options: options
)
end
Capybara.javascript_driver = :chrome
(For maintainers)
You can publish a new release to the buildpack registry by running the following commands:
pack buildpack package --publish reenhanced/buildpack-chrome-with-chromedriver