opening up whitelist for local setup with docker-compose

[skrdgraph]

Issue & Fix (in PR)

The existing docker-compose files cause the following errors when trying to interact with dgraphDB:

Sudhishs-MacBook-Pro:Desktop sudhishkr$ curl -X POST localhost:8080/admin/schema --data-binary '@schema.graphql'
{"errors":[{"message":"resolving updateGQLSchema failed because unauthorized ip address: 172.18.0.1 (Locations: [{Line: 3, Column: 4}])","extensions":{"code":"Error"}}]}

The issue here is unauthorized ip address, caused because of whitelist settings. The fix is listed in the article here. The default dgraphDB setting to 127.0.0.1 creates the above problem - and this fix should help ease spinning up the setup locally.

Why is this needed?

• to Test local execution without minikube or k8s by directly running on top of docker-compose
• this helps local testing

[CLAassistant]

All committers have signed the CLA.

[skrdgraph]

Looks to be working better now on local environment:

Sudhishs-MacBook-Pro:Desktop sudhishkr$ curl -X POST localhost:8080/admin/schema --data-binary '@schema.graphql'
{"data":{"code":"Success","message":"Done"}}

@darkn3rd ^ - it's now locked to private cidrs

[skrdgraph]

@akon-dey could we get this in? there is a separate PR for tests which is being worked on, and the docker-compose changes will not affect any CI / tests as it stands.