James
03/13/2018, 9:48 PMJames
03/13/2018, 9:50 PM{countUsers}
or something, and have them sent as 1 hit to graphql, which will translate into something like select count(*) from users where tenant_id=$ID
where $ID comes from a php _SESSIONMcArthur
03/13/2018, 11:32 PMdocker-compose up -d
but I get an ECONNREFUSED
when I deploy. Looking at the docker containers the status of prisma is always Restarting
. Makes me think it is just crashing on start and trying to start again. Anyone know how I might get logs or has run into a similar issue?McArthur
03/13/2018, 11:35 PMCould not resolve substitution to a value: ${SCHEMA_MANAGER_SECRET}
harmony
03/13/2018, 11:41 PMemerson
03/14/2018, 1:35 AMsjc67
03/14/2018, 2:50 AMMoritz
03/14/2018, 8:47 AMMoritz
03/14/2018, 8:48 AMsakhmedbayev
03/14/2018, 1:20 PMMoritz
03/14/2018, 1:55 PMError: ENOENT: no such file or directory, open 'XXX/src/generated/prisma.graphql'
. This is happening because prisma now names their generated files database
. I have the following script to work around: #!/bin/bash
set -x
rm -rf src/generated/
prisma deploy
graphql get-schema -p database -o src/generated/prisma.graphql
graphql prepare -p database -o src/generated
rm src/generated/prisma.graphql
cp src/generated/database.graphql src/generated/prisma.graphql
cp src/generated/database.ts src/generated/prisma.ts
However, I think prisma should take this task... Should I open a git issue? is there already one? Or am I missing some config?qsys
03/14/2018, 2:20 PMENV1="..."
ENV2="..."
qsys
03/14/2018, 2:22 PM$ graphcool deploy -e .env
[WARNING] in [...]/graphcool.yml: A valid environment variable to satisfy the declaration 'env:ENV1' could not be found.
[...]
qsys
03/14/2018, 2:22 PMgraphcool deploy --env-file .env
qsys
03/14/2018, 2:24 PM$ graphcool version
graphcool-framework/0.11.5 (linux-x64) node-v8.10.0
anton-b
03/14/2018, 3:03 PMpicosam
03/14/2018, 3:50 PM(next, source, args, ctx: Context)
) I cannot find what source
is really; anyone’s got a link to docs somewhere?johhansantana
03/14/2018, 3:50 PMWhoops. Looks like an internal server error. Search your cluster logs
KATT
03/14/2018, 3:51 PMKATT
03/14/2018, 3:51 PMWhoops. Looks like an internal server error. Search your cluster logs for request ID: api:api:cjer9jkbfaiig0905742fe7rf
johhansantana
03/14/2018, 3:51 PMMichael
03/14/2018, 3:53 PMnilan
03/14/2018, 4:14 PMMoritz
03/14/2018, 4:25 PMseed.graphql
?terion
03/14/2018, 4:46 PMMcArthur
03/14/2018, 4:58 PMMcArthur
03/14/2018, 4:58 PMThe server was not able to produce a timely response to your request.\r\nPlease try again in a short while!
manticarodrigo
03/14/2018, 6:50 PMrodmatos
03/14/2018, 7:35 PMpiscis
03/14/2018, 8:47 PM