menu

Prisma

๐Ÿ”ด The Prisma Spectrum community is not officially managed by Prisma's support team any more. Please seek help on GitHub or on Slack instead. Learn more: https://spectrum.chat/prisma/general/where-and-how-to-best-seek-help-with-questions-problems~687a1b8f-8658-4df3-8849-ea5ab3503f28

Channels
Chat
view-forward
# All channels
view-forward
# General
view-forward
# Beta
view-forward
# Community
view-forward
# GraphQL
view-forward
# OSS
view-forward
# Random
view-forward
Team

Prisma watercooler

March 20, 2019 at 8:32am
Show previous messages

July 6, 2019 at 11:36am
  • reply
  • like

July 8, 2019 at 12:28pm
and after executing below command prisma init getting error as
  • reply
  • like
  • reply
  • like

July 10, 2019 at 8:29am
Hi, I want to connect mariadb with ssl but prsima init and prisma introspect don't ask me to ssl option. how do I fix it?
  • reply
  • like

July 15, 2019 at 2:14pm
Use prisma internal field id value as a public resource identifier. Hello! I would like to implement a web application for a blog, where posts will be accessible via a URI, which will contain a unique identifier for each post. Is the public internal database identifier correct as a public resource identifier? Is it bad idea?
  • reply
  • like
i've had this problem before and don't remember how i resolved it, but i'm getting an error from deploying prisma. Basically a "deployment in progress" error because a deployment failed or something. Using docker-compose to connect to my postgres db that's hosted on elephantSQL.
  • reply
  • like

July 24, 2019 at 8:35pm
Is anyone else seeing despite already doing the update?
โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ
โ”‚ โ”‚
โ”‚ Update available 1.34.0 โ†’ 1.34.3 โ”‚
โ”‚ Run npm i -g prisma to update โ”‚
โ”‚ โ”‚
โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ
  • reply
  • like
Prisma CLI version: prisma/1.34.0 (darwin-x64) node-v10.4.1
Prisma server version: 1.34.3
  • reply
  • like
Hi, does anyone know why this error is?
  • reply
  • like

July 31, 2019 at 5:09pm
  • reply
  • like
This error appears Is the node version low๏ผŸ
  • reply
  • like

August 4, 2019 at 6:59pm
wewe
  • reply
  • like
eq
  • reply
  • like

August 29, 2019 at 6:20pm
Hello...Please help me out with this error. already tried changing docker-compose file but same error.
  • reply
  • like
Docker-Compose
version: '3'
services:
prisma:
image: prismagraphql/prisma:1.11
restart: always
ports:
- "4466:4466"
environment:
PRISMA_CONFIG: |
port: 4466
# uncomment the next line and provide the env var PRISMA_MANAGEMENT_API_SECRET=my-secret to activate cluster security
# managementApiSecret: my-secret
databases:
default:
connector: mongodb
host: 192.168.65.2
port: '4406'
database: truck.pe
schema: public
user: admin
password: movies
migrations: false
  • reply
  • like
Docker-Compose
version: '3'
services:
prisma:
image: prismagraphql/prisma:1.11
restart: always
ports:
- "4466:4466"
environment:
PRISMA_CONFIG: |
port: 4466
# uncomment the next line and provide the env var PRISMA_MANAGEMENT_API_SECRET=my-secret to activate cluster security
# managementApiSecret: my-secret
databases:
default:
connector: mongodb
host: 192.168.65.2
port: '4406'
database: truck.pe
schema: public
user: admin
password: movies
migrations: false
Please do note that changing host: to host.docker.internal also not working
  • reply
  • like

September 3, 2019 at 7:49am
I added field Permission and got this error. Plz help me
  • reply
  • like

September 12, 2019 at 11:23am
I added field Permission and got this error. Plz help me
Just started getting the same issue using a similar set up to the stack used in Wesbos' sick fits. Was working fine about an hour ago and now this. Should be noted that I also can't view my service in the Prisma Console online.
  • reply
  • like
Show more messages