Welp, after some trial and error I’ve got it working. One other thing I did not say in my post was that I am running the dgraph servers on a development server but connecting to dgraph-ratel through the browser of my laptop. When I specify the development server’s local IP:8080 dgraph-ratel is able to connect. I swear I tried this before my original post but maybe some other changes I made were necessary as well (making a dgraph folder at “/” owned by root, then running each of the dgraph services as root from within this folder).
I did not expect dgraph-ratel to be configured from the client’s browser (and it’s ip) (and thus needing the local IP of the host dgraph server is running on (which also happens to be the host dgraph-ratel is running on)). I expected dgraph-ratel to try to connect to dgraph server from the server dgraph-ratel is running on (and thus localhost). I can see how this won’t matter when setting up an application to connect to the dgraph api (9080).
One thing I do not understand is the role of dgraph zero. Why are we connecting directly to one server node (in a one node cluster) rather than connecting to dgraph zero and letting it route our data to the appropriate dgraph server? Maybe I just need to go through the exercise of setting up multiple dgraph server nodes for it to become apparent. If there is a quick answer, feel free to let me know.
Anyway, thanks again!