is `PRISMA_MANAGEMENT_API_SECRET` still needed?
# orm-help
w
is
PRISMA_MANAGEMENT_API_SECRET
still needed?
n
It was never "needed" in the sense of being an obligatory option. But yes, setting this value in the
PRISMA_CONFIG
is the way to go to to secure your management API with a secret.
w
is this the same as securing the prisma server with JWT ?
n
I don't know what you refer to.
w
PRISMA_MANAGEMENT_API_SECRET
and
SECRET
in prisma.yml are NOT the same thing?
n
that's correct. (it's
secret
not
SECRET
by the way)
w
of course πŸ™‚
n
1. `PRISMA_MANAGEMENT_API_SECRET`: secure the management API of a Prisma server 2. `secret`: secure the GraphQL API of a single Prisma service
w
i would
PRISMA_MANAGEMENT_API_SECRET
if i would be deploying it outside of prisma.sh, like AWS. is that correct?
n
that's correct
You don't want anyone to use your management API who isn't authorized to do so
w
mhm. thanks πŸ™‚
πŸ‘ 1
i hope i’ll be able to show a bit the project im building. spoilers … photography, images, DAG and graphql powered by prisma πŸ™‚
🦜 1
n
what's DAG?
to me it means directed acyclic graphs πŸ˜„
w
directed acyclic graph
gucci 1
πŸ˜„ 1
in essence i’m trying to solve my own problem by creating proof-of-work for photos that everyone can use. also idea is to β€˜open’ the Lightroom to other services without installing the publishers or learning Lua πŸ˜‰
πŸ‘Œ 1