I'm newly (returning) to prisma, but on the <app.p...
# orm-help
r
I'm newly (returning) to prisma, but on the app.prisma.io site, the new service I make is perpetually stuck on "Waiting for the deployment..." - even though the
prisma deploy
is successful (or at least doesn't error). Is there some bug, or way to force it or is there some issue with the prisma online bits?
h
I am seeing this for the first time so can you please share a screenshot 🙏
r
I think I found the cause of this particular issue - when I was `init`'ing, I was creating a new project, not the service I made on the site.
(which it seemed I had to enable 3rd party cookies to work)
but now I'm seeing this https://cloudup.com/cwjwe26-3Kh
com.prisma.deploy.schema.InvalidProjectId: No service with name 'default' and stage 'default' found","query
h
Have you deployed your prisma service yet
via
prisma deploy
r
the
com…
error was the result of the first deploy
s
I had this problem and in the prisma config file needed to match up the stage to the prisma cloud setup. In my case I’d set up “production” as the stage when setting up the prisma.yml file but somewhere was using “default” instead. Making sure that matches, and the URL has the same stage in it seemed to fix the deploying issue.
👍 1
In prisma.yml I ended up with something like:
endpoint: <https://my-cluster.now.sh/my-prisma/production>
(although I’d advise against using Now for this - it was slow as hell)
r
@stef ah, it might be that. IIRC I used "dev" on prisma.io and I think it's doing "default" via the cli - will check 👍