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

Changes in config.ini.example #1541

Closed
wants to merge 1 commit into from
Closed

Changes in config.ini.example #1541

wants to merge 1 commit into from

Conversation

Beri51
Copy link

@Beri51 Beri51 commented Nov 14, 2016

Description

I just added some parameters in the config.ini file.
I do not know if this is wanted but as I had some light troubles yesterday with the 2captcha parameters, I thought this could help other beginners.

This is my very first commit/PR, I hope I did this right.

Motivation and Context

Description and names of parameters from PR 1526 wee not perfectly accurate to use in the config.ini file.

How Has This Been Tested?

Raspberry Pi using latest version including PR 1536

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
    None of the above (I guess)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

Added 2captcha parameters, jitter, accountcsv

@Beri51 Beri51 changed the title Changes in config.ini.examples 2Captchas (and minor changes) in config.ini.examples Nov 14, 2016
@Beri51 Beri51 changed the title 2Captchas (and minor changes) in config.ini.examples Changes in config.ini.example Nov 14, 2016
@chowder
Copy link
Contributor

chowder commented Nov 15, 2016

The captcha-dsk field is set to 6LeeTScTAAAAADqvhqVMhPpr_vB9D364Ia-1dSgK by default, you don't need to do that again in config.ini; the comment for it can stay, though.

@Beri51
Copy link
Author

Beri51 commented Nov 17, 2016

Changes not really needed, anybody should be able to do it manually.
So I guess I close this PR myself ;-)

@Beri51 Beri51 closed this Nov 17, 2016
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

Successfully merging this pull request may close these issues.

None yet

2 participants