Abhischek
06/30/2020, 12:36 PMRyan
06/30/2020, 12:38 PMAbhischek
06/30/2020, 12:40 PMRyan
06/30/2020, 12:42 PMAbhischek
06/30/2020, 12:45 PMRyan
06/30/2020, 12:47 PMAbhischek
06/30/2020, 12:51 PMRyan
06/30/2020, 12:53 PMAbhischek
07/01/2020, 9:45 AMgraphql-yoga
which I've packaged as another docker container. I need to supply the prisma endpoint URL to this container, they're part of the same AWS VPC.
We are doing:
"environment": [
{
"name": "ENDPOINT",
"value": "<http://localhost:4466>"
},
but that doesn't seem to work. Do you know how to address the prisma container in the prisma.yml
when they're deployed as a separate container?Ryan
07/01/2020, 9:55 AMlocalhost
?Abhischek
07/01/2020, 12:40 PMINFO] Fatal error during deployment worker initialization: com.mongodb.MongoTimeoutException: Timed out after 30000 ms
Ryan
07/01/2020, 12:56 PMAbhischek
07/01/2020, 1:00 PMAbhischek
07/01/2020, 1:58 PMawsvpc
then you can access other containers you are deploying by the localhost
interface. So I passed http://localhost:4466 to my graphql - server to connect to prisma.
More details here: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-networking.htmlOmar Nasr
07/05/2020, 6:26 PMAbhischek
07/17/2020, 10:45 AMPRISMA_CONFIG
? Assuming that you are using Mongo