Hi all :wave: New here. -- The app I'm working on ...
# orm-help
c
Hi all šŸ‘‹ New here. -- The app I'm working on (react CRA only, no B/E) uses Prisma1 on demo with https://app.prisma.io/. It's a MVP/Beta no trafic as of today. Before launch I have a few concerns : • how much can we rely (if it's even an option) on https://app.prisma.io/ before an install on our own server becomes mandatory? • how demanding is the migration from prisma1 to prisma2? • how do I know what kind of server size I need to host prisma2? • what is the easiest (as easy as the demo) way to use prisma ? Thanks šŸ™
a
I recently started working on a legacy project with Prisma 1. In a nutshell, It's not a good experience. Little bit drives you crazy. Search Engine links for Issues/Solutions are broken, Sometimes like in Prisma1 docs to other pages are broken. GitHub issues are hard to find because they moved Prisma1 repo from
/prisma
to
prisma1
an now
/prisma
repo is for Prism2 repo. And sometimes cherry on top you find issues in GraphCool repo/issue boards. Everything else is AWESOME....
šŸ‘Œ 1
šŸ˜„
l
I started a new project on prisma 1 some months back, mainly because prisma 2 doesn't support mongo yet
Using mongo hosted elsewhere weren't possible (as far as I could tell) from app.prisma.io, so I quickly ditched that. In addition I needed certificates in my prisma for it to be able to communicate with the DB, so I pretty soon had to build my own prisma docker image, and when I had that, I went the Heroku route.
šŸ‘Œ 1
My app is still pre-release, so not very worried about resource use yet, but I expect Heroku to be easy enough to scale up as needed.
šŸ’Ŗ 1
c
Thanks @Ahmad @Lars Ivar Igesund
😊 1