rohanray
01/28/2018, 2:52 AMsorenbs
sorenbs
sorenbs
prisma token
and then construct the header like this: {"Authorization": "paste the token"}
rohanray
01/28/2018, 3:12 AMrohanray
01/28/2018, 3:12 AMrohanray
01/28/2018, 3:12 AMrohanray
01/28/2018, 3:13 AMrohanray
01/28/2018, 3:17 AMrohanray
01/28/2018, 3:20 AMsorenbs
sorenbs
localhost
instead of the correct iprohanray
01/28/2018, 4:01 AMrohanray
01/28/2018, 4:01 AMgraphqlconfig
which is on the DO serverrohanray
01/28/2018, 4:01 AMrohanray
01/28/2018, 4:02 AMprojects:
app:
schemaPath: "src/schema.graphql"
extensions:
endpoints:
default: "<http://localhost:4000>"
database:
schemaPath: "src/generated/prisma.graphql"
extensions:
prisma: database/prisma.yml
prepare-binding:
output: src/generated/prisma.ts
generator: prisma-ts
rohanray
01/28/2018, 4:03 AMrohanray
01/28/2018, 4:06 AMrohanray
01/28/2018, 4:07 AMprojects:
app:
schemaPath: "src/schema.graphql"
extensions:
endpoints:
default: "<http://139.59.80.18:4000>"
database:
schemaPath: "src/generated/prisma.graphql"
extensions:
prisma: database/prisma.yml
prepare-binding:
output: src/generated/prisma.ts
generator: prisma-ts
rohanray
01/28/2018, 4:11 AMhttp://<IP>:4466/cric-prisma/prod
as per your suggestion and it works πrohanray
01/28/2018, 4:12 AMrohanray
01/28/2018, 4:12 AMrohanray
01/28/2018, 4:15 AMrohanray
01/28/2018, 4:16 AMlocalhost:4466
rohanray
01/28/2018, 4:22 AMrohanray
01/28/2018, 4:24 AMagartha
01/28/2018, 4:36 AMprisma.yml
point to the correct cluster on your local machine?agartha
01/28/2018, 4:36 AMprisma.yml
sorenbs
rohanray
01/28/2018, 4:55 AMrohanray
01/28/2018, 4:57 AM<DO_IP>:3000/playground
from my local machine. Not sure if my local prisma.yml
will affect thatrohanray
01/28/2018, 4:57 AMagartha
01/28/2018, 4:58 AMagartha
01/28/2018, 4:58 AM.graphqlconfig
filerohanray
01/28/2018, 4:59 AMagartha
01/28/2018, 4:59 AM.graphqlconfig
fileagartha
01/28/2018, 4:59 AMrohanray
01/28/2018, 5:00 AMagartha
01/28/2018, 5:00 AMagartha
01/28/2018, 5:01 AMrohanray
01/28/2018, 5:02 AMNODE_ENV="production"
PRISMA_STAGE="prod"
PRISMA_ENDPOINT="<http://1xx.xx.xx:4466/cric-prisma/prod>"
PRISMA_CLUSTER="local"
PRISMA_SECRET="xxx"
APP_SECRET="xxx"
S3_BUCKET="jpl-cric"
S3_KEY="xxx"
S3_SECRET="xxx"
rohanray
01/28/2018, 5:02 AM.env
file on DOagartha
01/28/2018, 5:02 AMagartha
01/28/2018, 5:02 AMrohanray
01/28/2018, 5:02 AMservice: cric-prisma
# the cluster and stage the service is deployed to
stage: ${env:PRISMA_STAGE}
# to disable authentication:
# disableAuth: true
secret: ${env:PRISMA_SECRET}
# the file path pointing to your data model
datamodel:
- datamodel/types.graphql
- datamodel/enums.graphql
# seed your service with initial data
#seed:
# import: seed.graphql
cluster: ${env:PRISMA_CLUSTER}
#START CUSTOM RORAY
# Path where the full GraphQL schema will be written to
# after deploying. Note that it is generated based on your
# data model.
agartha
01/28/2018, 5:03 AMagartha
01/28/2018, 5:03 AMrohanray
01/28/2018, 5:04 AMprojects:
app:
schemaPath: "src/schema.graphql"
extensions:
endpoints:
default: "<http://localhost:4000>"
database:
schemaPath: "src/generated/prisma.graphql"
extensions:
prisma: database/prisma.yml
prepare-binding:
output: src/generated/prisma.ts
generator: prisma-tsprojects:
app:
schemaPath: "src/schema.graphql"
extensions:
endpoints:
default: "<http://localhost:4000>"
database:
schemaPath: "src/generated/prisma.graphql"
extensions:
prisma: database/prisma.yml
prepare-binding:
output: src/generated/prisma.ts
generator: prisma-ts
rohanray
01/28/2018, 5:05 AMgraphcoolrc
file on DO serveragartha
01/28/2018, 5:05 AMagartha
01/28/2018, 5:06 AM~/.graphcoolrc
looks something like this:
graphcool-1.0:
cloudSessionKey: >-
eyJhb...
clusters:
local:
host: '<http://localhost:60000>'
clusterSecret: "-----BEGIN RSA PRIVATE KEY-----\r\nMIIEo....
rohanray
01/28/2018, 5:06 AMrohanray
01/28/2018, 5:06 AM.graphcoolrc
file at ~
rohanray
01/28/2018, 5:07 AM~/prisma/config.yml
looks like belowrohanray
01/28/2018, 5:07 AMclusters:
local:
host: '<http://localhost:4466>'
clusterSecret: "-----BEGIN RSA PRIVATE KEY-----\r\nMIIEogIBAAKCAQEAncTGcWRLFPsm6zQu+ND3CwQSAg45eIJ23UL1w5srCXVTrJmr\r\nMFfV5YERP0sdxCfryksl2ZWetZgndEsvKW5MOX5qPuDaGx8kIzyvZDci8nLwVyUj\r\nUHbYmRkTFFdDIRqwQSt/3yxiHTeh9l0KTiFH69TsZEoYJnCaEjfOGhm9cqivLuwS\r\nxJL8hVwzx4ntIxSAw7zmmD+o9xfNEx+21eyyajFJshkjELea .....
agartha
01/28/2018, 5:07 AMagartha
01/28/2018, 5:07 AMagartha
01/28/2018, 5:08 AMhost
you see in there is the one the playground usesagartha
01/28/2018, 5:08 AMrohanray
01/28/2018, 5:08 AMagartha
01/28/2018, 5:08 AMrohanray
01/28/2018, 5:09 AMgraphql-yoga
server... or graphql-yoga
server uses database/prisma.yml
file for prisma endpoint lcoationagartha
01/28/2018, 5:09 AMagartha
01/28/2018, 5:10 AMagartha
01/28/2018, 5:11 AMagartha
01/28/2018, 5:11 AMprisma deploy
uses that host to deploy to your clusterrohanray
01/28/2018, 5:12 AMagartha
01/28/2018, 5:12 AMgraphql-yoga
server uses whatever you have specified on your binding in the index.js or .ts fileagartha
01/28/2018, 5:13 AMrohanray
01/28/2018, 5:14 AMagartha
01/28/2018, 5:14 AMrohanray
01/28/2018, 5:15 AMrohanray
01/28/2018, 5:15 AMagartha
01/28/2018, 5:15 AMprisma deploy
, as I assume the cluster is reachable on its external IP while deploying as well, but make sure to test that.rohanray
01/28/2018, 5:16 AMagartha
01/28/2018, 5:16 AMrohanray
01/28/2018, 5:17 AMprisma deploy
Iagartha
01/28/2018, 5:18 AM~/.prisma/config.yml
to your local machine and deploy directly from your own machinerohanray
01/28/2018, 5:18 AMagartha
01/28/2018, 5:19 AMrohanray
01/28/2018, 5:19 AMrohanray
01/28/2018, 5:19 AMagartha
01/28/2018, 5:19 AMrohanray
01/28/2018, 5:21 AMrohanray
01/28/2018, 5:21 AMrohanray
01/28/2018, 5:22 AMrohanray
01/28/2018, 5:22 AMagartha
01/28/2018, 5:22 AMrohanray
01/28/2018, 5:22 AMagartha
01/28/2018, 5:22 AMrohanray
01/28/2018, 5:23 AMagartha
01/28/2018, 5:23 AMagartha
01/28/2018, 5:23 AMrohanray
01/28/2018, 5:24 AMrohanray
01/28/2018, 5:24 AMrohanray
01/28/2018, 5:26 AMrohanray
01/28/2018, 5:26 AMagartha
01/28/2018, 5:26 AMagartha
01/28/2018, 5:27 AMrohanray
01/28/2018, 5:27 AMrohanray
01/28/2018, 5:27 AMrohanray
01/28/2018, 5:28 AMagartha
01/28/2018, 5:28 AMagartha
01/28/2018, 5:28 AMrohanray
01/28/2018, 5:28 AMagartha
01/28/2018, 5:28 AMagartha
01/28/2018, 5:29 AMrohanray
01/28/2018, 5:29 AMrohanray
01/28/2018, 5:29 AMrohanray
01/28/2018, 5:29 AMagartha
01/28/2018, 5:30 AMagartha
01/28/2018, 5:30 AMagartha
01/28/2018, 5:31 AMrohanray
01/28/2018, 5:32 AMmohawk2
01/28/2018, 6:13 AM