Add documentation on areas that people will need to change if they launch their own deployment of OpenOversight

[McEileen]

If people are interested in launching their own deployment of OpenOversight, such as BPD Watch or cops.photo, they'll need to customize certain areas of the codebase.

It's especially important for people to change the contact section, otherwise emails might go to the wrong group.

Here's a rough list of areas that people would need to customize

• The legal section on the "about" page
• The contact and media section on the "about" page
• The social media and email links in the base.html template

[brianmwaters]

We should make sure they change "OpenOversight" in some places so users don't get unduly confused between OO the software and OO the website. Maybe most of this can be done through a configuration file or something

[brianmwaters]

Actually - is there a diff from bpdwatch.com we could use as a starting point for making this configurable at install time? Ping @dismantl

[AetherUnbound]

Hey folks! I'd also be really interested in some documentation on where to start with a dockerized version of this. From the looks of the provided compose file, that one appears to be for testing and not necessarily production use.