Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation on kaleido/chrome for server #4952

Open
builder173 opened this issue Dec 26, 2024 · 0 comments
Open

Documentation on kaleido/chrome for server #4952

builder173 opened this issue Dec 26, 2024 · 0 comments

Comments

@builder173
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant