Add instructions on how to set up a secure development environment to the documentation

[Afrowave]

Description

Facebook have moved their users to secure by default.

Rationale

If a developer chooses to build Facebook login capability with the users app, then setting https in the developer environment will be necessary.

If required, I can add this capability through a new PR so that it becomes part of the project configuration.

[Afrowave]

Thanks @browniebroke for having a look at this.

[browniebroke]

Thanks for the addition, @Afrowave

[browniebroke]

As a side note for next time, could you please use a feature branch (as opposed to using master in your fork) to send your pull request? That would avoid the extra commits that we can see in here, like the one from #2661.

[Andrew-Chen-Wang]

@browniebroke I don't believe this is necessary since django-allauth doesn't require social login capabilities to be in an HTTPS local machine environment ref #2759 which raised this methodology. I haven't tested a social login with Facebook's OAuth2 capabilities, but AFAIK with Stripe and other OAuth apps, this isn't necessary and the docs might be suggesting something that's not really suitable for the local development environment.

[Afrowave]

I am sorry, @browniebroke,

I meant to get round to this and fix it now that the docs run in a docker container. I will fix this and also write a blog post to this. I have given myself the task of amintaining this part of the docs.

I actually thought I had set up notifications. I hope that is okay with you.