``` ➜ lyra-api prisma deploy Deploying service `d...
# orm-help
l
Copy code
➜  lyra-api prisma deploy
Deploying service `default` to stage `default` to server `local` 79ms
Service is already up to date.

post-deploy:
 ▸    generate is not a prisma command.
 ▸    Perhaps you meant cluster-token
 ▸    Run prisma help for a list of available commands.

Get in touch if you need help: <https://www.prisma.io/forum/>
To get more detailed output, run $ export DEBUG="*"

Running prisma generate ✖
➜  lyra-api prisma | grep generate
  generate        Generate a schema or Prisma Bindings
➜  lyra-api
d
This is a known issue if you installed Prisma beta via
brew
. You can manually run
prisma generate
after
prisma deploy
as a workaround. We will work on a fix shortly 👍
e
@Luke Run "prisma -v" and see which version your machine is using. I had the same problem, I installed Prisma via brew but the first time I installed Prisma was via NPM. So I had to install the Prisma 1.17 beta version again with NPM to make my system actually use the beta version. There is probably a better solution to that, to make your system use the version you want but that is how I fixed it for now for myself
l
@Entrepreneur3 Thanks! Is there a difference between
prisma generate
and
Copy code
- graphql get-schema -p prisma
- graphql codegen
it seems like generate does both of those commands?
n
prisma generate
generates the new Prisma Client, while
graphql codegen
generates a GraphQL Binding. Those are different.