graphql-boilerplates/node-graphql-server

Handle environments with other ports than 60000

marktani opened this issue · 1 comments

Some environments already use port 60000 which means graphcool-dev runs on 60001, or potentially another port. graphcool-framework runs on 60000, too. So it's quite likely that you end up with port 60001 for graphcool.

All boilerplates hardcode the port 60000 which leads to problems like this.

Is there a way to detect the graphcool port dynamically and use this value instead of a hardcoded port?

This issue was moved to graphcool/framework#1475