Description
I'm trying out the release candidate builds for plotly.py and kaleido. I saw the note about chrome (or?) chromium needing to be available to kaleido now since it isn't built with that dependency. I didn't see guidance on how to accomplish that in a robust way for a python server environment. (I'm creating static images for pdfs)
What I tried:
The heroku chrome build-pack per this page
remote: Installed Chrome dependencies for heroku-24
remote: Adding executables to PATH
remote: /tmp/build_f25b7b65/.chrome-for-testing/chrome-linux64/chrome
remote: /tmp/build_f25b7b65/.chrome-for-testing/chromedriver-linux64/chromedriver
remote: Installed Chrome for Testing STABLE version 131.0.6778.204
What happened:
Still getting runtime error and don't think I can reliably use the BROWSER_PATH to point plotly to this installation.
RuntimeError: Kaleido now requires that chrome/chromium is installed separately. Kaleido will try to detect it automatically, but the environmental error "BROWSER_PATH" can also be set