Configurable webdriver (gecko by default but now chrome can be chosen) #70
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've added the chromedriver configurable with the
config.yaml
file.You can configure this in the
config.yaml
. The keys are the following ones.Geckodriver
The
geckodriver
is properly defined by default. In case you need to configure it, then:Chromedriver
If you want to use
chromedriver
locally, then you should leave the config this way:Using chromedriver in Heroku
If you use Heroku, then you have to add the Heroku chromedriver buildpack.
And then use the environment vars provided automatically by it.
This is added in the readme