Add a way to disable ReCAPTCHA during development

[Minoru]

It'd be nice to flip a toggle or something and be able to develop locally without worrying about ReCAPTCHA. As it is, I had to edit a couple of files to make Loglist believe that CAPTCHA check was passed successfully.

[rexim]

This is strange. ReCAPTCHA should work if your host is localhost.

[ForNeVeR]

Maybe he wanted to edit the files without an active internet connection? I think that's a valid point.

[rexim]

@Minoru did you, really?

[rexim]

Anyway, we have config for such things. Feel free to add an option.

[Minoru]

I have an active Internet connection. No, I didn't try to work on LogList without one. Still, ReCAPTCHA doesn't work, claiming I have invalid site key. The docs claim that "[b]y default, all keys work on "localhost" (or "127.0.0.1"), so you can always develop and test on your local machine.", but that doesn't seem to be the case. Any advice?

[Minoru]

JFTR, I didn't edit RECAPTCHA_{PUBLIC,PRIVATE}_KEY settings in devenv file. Should I?

[rexim]

Hah! Looks like Mr @ForNeVeR and I use the the same keys that are in production! :D

[rexim]

That's why everything work for us.

[rexim]

You can create your own RECAPTCHA keys if you want

[Minoru]

Yeah, so it turns out I should generate and specify valid keys in order for ReCAPTCHA to work. I'll update the README in the moment.

[ForNeVeR]

It seems that you need to obtain your own key even to use it on localhost. I think that we should add an option to disable CAPTCHA. It will be easier for our contributors to install local instances without registration and SMS, you know.

[Minoru]

I don't see a clear way to add an option, so the only thing I can do right now is clarify the docs. Will such a PR be welcome?

[ForNeVeR]

Yes, it will be good (but not enough). I guess someone else could later resolve the issue completely.