Hi, I'm Stephen. I write about Terraform, CI/CD, and full-stack dev. Built the official Prisma 2.0 course (20k students). Now building deploycompare.com: is this Terraform deploy normal?
Hey, I have a question, in the index page you import the type NextPage, although I don't see you use getInitialProps or something similar, is there any reason for you to put "import {NextPage} from 'next'" or it's just simple convention?
Hi, I'm Stephen. I write about Terraform, CI/CD, and full-stack dev. Built the official Prisma 2.0 course (20k students). Now building deploycompare.com: is this Terraform deploy normal?
Hi Jose! That's a great catch- I just checked and you definitely don't need to import NextPage there, you can simply define your page component as a function and export that. I'll be sure to update the code- thanks!
Hi, I'm Stephen. I write about Terraform, CI/CD, and full-stack dev. Built the official Prisma 2.0 course (20k students). Now building deploycompare.com: is this Terraform deploy normal?
Hi, I'm Stephen. I write about Terraform, CI/CD, and full-stack dev. Built the official Prisma 2.0 course (20k students). Now building deploycompare.com: is this Terraform deploy normal?
Can you tell in your terminal what the error is? You should see that docker-compose is listing the output of all your containers and you can look at what is going on with the frontend container. I wonder if you ran npm stop and npm start if that would fix it. Maybe some error happened during the build of the frontend container.
Hi, I'm Stephen. I write about Terraform, CI/CD, and full-stack dev. Built the official Prisma 2.0 course (20k students). Now building deploycompare.com: is this Terraform deploy normal?
Hey, just noticed one small thing that needs updating since prisma just updated prisma2..
The article says: "Let's fix that by updating backend/prisma/project.prisma file"
The project.prisma file has now been renamed to schema.prisma (see: github.com/prisma/prisma2/releases...)
Awesome thanks for letting me know! I'll fix it ASAP. Thanks for reading!
Hey, I have a question, in the index page you import the type NextPage, although I don't see you use getInitialProps or something similar, is there any reason for you to put "import {NextPage} from 'next'" or it's just simple convention?
Hi Jose! That's a great catch- I just checked and you definitely don't need to import NextPage there, you can simply define your page component as a function and export that. I'll be sure to update the code- thanks!
@codemochi Excellent post. Waiting for the Part 2 of this series.
Thanks Nirmal! I'll do you one better- we have part 2 and 3 out as of today! Check out the top of this post for the series links to the other posts on dev.to or go straight to the source:
codemochi.com/blog/2019-07-10-pris...
codemochi.com/blog/2019-07-12-pris...
Cheers!
Thanks CodeMochi.
I am getting this error when i cloned from the github.
Am i missing something. But i can able to access the GraphQL Playground and not the App from 3000 port.
Can you tell in your terminal what the error is? You should see that docker-compose is listing the output of all your containers and you can look at what is going on with the frontend container. I wonder if you ran
npm stopandnpm startif that would fix it. Maybe some error happened during the build of the frontend container.Nice! Btw Next.js v9 dropped today so it might be a good idea to update the section that talks about the Canary version. V9 has typescript support :)
Super sweet, I'll update that too. Thanks Bruno!
Very cool !!!