Update boilerplate setup

Question

Update boilerplate setup

kbrandwijk opened this issue 7 years ago · 5 comments

kbrandwijk commented 7 years ago

Call gc deploy from install script
Remove default cluster from 'graphcool.yml'
Ping nearest cluster (for fullstack only) -> on hold until graphcool cli offers this again
Write endpoint to .env after deployment

^^ In all boilerplates

Answer 1 · 2018-01-06T00:10:51.000Z

why do you want to ping the nearest cluster? I think the local cluster is the preferred option.

Answer 2 · 2018-01-06T00:53:45.000Z

As discussed with @schickling, for fullstack boilerplates/examples, the (nearest) new public cloud cluster should be the default. For server boilerplates, there should be no default.

Answer 3 · 2018-01-06T03:30:33.000Z

@schickling Can we put the install script in a separate package, and require that in the .install folder, instead of copy pasting the same install script to each and every boilerplate? This would make it a lot more maintainable, and you always have only 1 dependency for installation.

Answer 4 · 2018-01-06T04:11:48.000Z

Current version: see https://github.com/graphql-boilerplates/node-graphql-server/tree/installpathtest/basic/.install

Answer 5 · 2018-01-06T04:30:14.000Z

~~https://github.com/graphcool/framework/issues/1525 is blocking for writing to the .env file~~