Jo
08/05/2019, 8:43 PMHarshit
08/06/2019, 3:38 AMservice$stage
. This is controlled by the last two routes of the url. So if your endpoint is https://example.com/backend/dev
It will map to backend$dev
schema in postgres and backend@dev
in MySQL.
If you don't provide any service and stage name, it default name is default$default
Jo
08/06/2019, 6:43 AMJo
08/14/2019, 9:57 PMRyan Rickerts
08/14/2019, 10:47 PMdefault@default
in MySQL and completely started over so everything matched this convention, I am still getting the same error when I go to load the admin endpoint. So Iām looking at my endpoint in src/prisma/prisma.service.ts
thinking that is the problem. Everything else is working, but the error I get is the same: āNo service with name ādefaultā and stage ādefaultā foundā even though I havenāt changed anything from the default. @Harshit where do you provide the service and stage name?Ryan Rickerts
08/15/2019, 12:12 AMdefault
service everywhere: $ prisma reset
? Are you sure that you want to reset the data of default in stage default? y/N y
Resetting default@default 345ms
$ prisma deploy
Deploying service `default` to stage `default` to server `local` 1.0s
Service is already up to date.
Ryan Rickerts
08/15/2019, 6:06 PMnestjs-prisma$ cat prisma.yml
endpoint: <http://localhost:4466/projectName/dev>
datamodel: datamodel.prisma
so my service is now projectName
and stage is dev
and the MySQL database is called proteus@dev