create-prisma-app v1.5.11

Create Prisma App

✨ Setup environments sophisticated Prisma back end in just one command!

Important

⚠️ Breaking change in Prisma v1.28 and this template v1.5.0 + is intended to accommodate the change

Installation

npm i -g create-prisma-app
create-prisma-app MyPrismaApp

OR

npx create-prisma-app MyPrismaApp

🐝 If your docker unable to run this package then you may need Docker v18.06 +.

Quick Start

Dev Environment Quick Start

start:

npm run dev-setup

☀️ It is ok to always use dev-setup to start dev

shut down:

npm run dev-down

then Ctrl + C to terminate Node in terminal

Test Environment Quick Start

start:

npm run test-setup # for 1st time only (run this again for different docker file setting)
npm run test-up #⚡ for 2nd time and above(do not run test-up soon after test-setup, it is unnecessary)

shut down:

npm run test-down

🚩 test-start, test-deploy and test-schema automatically run in container and doesn't work outside the of the container(remember unlike dev environment, test and prod Node is running in container)

Prod Environment Quick Start

Prod is very similar to test, so the instructions also similar:

start:

npm run prod-setup # 1st time only (run this again for different docker file setting)
npm run prod-up # ⚡️ for 2nd time and above(do not run prod-up soon after prod-setup, it is unnecessary)

shut down:

npm run prod-down

🚩 prod start, prod-deploy and prod-schema automatically run in container and doesn't work outside the of the container(remember unlike dev environment, test and prod Node is running in container)

Jest Environment Quick Start

1. in ./.config/jest.env, change the value of PRISMA_ENDPOINT to match dev or test.

🐠 Jest run on Prisma endpoint not Node endpoint

⚠️ important: do not run jest on production because jest delete database in the beginning of run, that is why there is no jest-prod config file!

Configuration

Most configurations are exposed already exposed in ./.config folder, read comments in dev.env to have better understanding what each variable does.

Scripts

The scripts may look overwhelming, but it is actually repetitive in pattern, what the scripts do are also very straight forward, they are like the scripts that you frequently use, just more organized and accessible.

Troubleshooting

Unexpected End of JSON Input During Installation

👿 npm cache corrupted
😇 run npm cache clean --force to fix it

"Project default\$default Not Found"

👿 mostly when running test or prod, this is due to Node server is ready before Prisma server and fail to deploy schema, this happen if your server is sleeping and prisma need time to establish connection.
😇 the solution is easy, increase delay of wait-prisma scripts in package.json.
👷 will add checking mechanism in future.

"Internal Server Error"

👿 mostly when running test or prod, could be many reason, most possible reason is Node unable to connect with Prima due to .env variables misconfiguration.
😇 if your config is correct but has this error, wait a while and keep trying; if not check your .env variables configuration.

Graphql Playground Shows Blank Page After dev or test Setup

👿 Node fail or haven't establish the connection with Prisma server
😇 the solution is easy, just wait and refresh the page or increase delay of wait-prisma npm scripts in package.json.

Port is Already Allocated Error

👿 it is most likely you have another program like postgres installed and running with 5433 port.
😇 change PSQL_PORT variable in ./.config/xxx.env, xxx is dev or test or prod.

Architecture

This package is aim to get you up and running in different environments, in general there are 4 types of environments:

1. dev(dev.env) Ideally dev is an environment that allow us to code and experimenting our thing even without internet. It is an environment that we can carry on planning and creating without relying third party service such as server on AWS, instead we should have a server that we can toy with anytime in our computer.

2. prod(prod.env) Prod is the environment where we want to treat our data, data model and configuration delicately. Imagine if we accidentally deploy our dev data and configuration into prod, that would be hell unleashed.For some cases we can mix up test and dev environments and that is tolerable, but production environment must has it own space.

3. test(test.env) Ideally the test environment should be as similar as prod environment as possible so that we can expect the same behavior when we deploy it, do not confuse this with jest.

4. jest(jest.env) Do not confuse this with test, jest has its own environment variables that points to test environment from outside world, in short jest are interaction from real world upon this dev, test and ci environment.

To summarize it:

✈️ You can always change the architecure, simply modify the docker(compose) files and change the variables in ./.config accordingly

Docker refuses to add a key that allows user chooses to run a service or not even though it is a highly requested feature.

The implication is we are unable to share the same docker-compose file for all modes, especially dev mode because dev mode run Node outside docker.

I have no choice but to create a separated docker yml file for dev. Yes we can use --scale service=0 command, but that doesn't stop docker wasting time building the service and building Node every time user run dev mode.

Prerequisite

Knowledge:

1. Graphql
2. Prisma

Tools:

1. Docker
2. Kitematic(optional): Docker GUI 🚲
3. DBeaver(optional): SQL database GUI 🚲

🚲 With or without Kitematic and DBeaver, we still able to get the app running, but I recommend them because they are very useful especially DBeaver.

Extra Benefits

1. commit hooked prettier styling
2. Babel env preset, write ES6️⃣ right away!
3. basic data model
4. basic schema
5. basic api call
6. basic Jest test
7. basic CircleCI configuration file
8. basic JWT authentication
9. modularity, replace any dependency you want.

Documentation

The scripts is extended to 5 parts:

• basic
• jest
• prod
• test
• dev

1. prod, test and dev are derived from basic script.
2. The scripts are mostly structured in the same way: prod and test scripts have 99% of similarity.
3. The 1% is test-setup will open server endpoint in browser when it is ready.
4. test will fails to open the browser in Ubuntu but it does no harm while prod-setup will not.
5. dev has slightly more scripts and much loosely structured so that you can develope with more flexible scripts.
6. jest only has 2 scripts.

Please study ./config/dev.env for better understanding on how each environment variable works.

Here is doc for scripts:

🚩 Automatically run in container and doesn't work outside the of the container(remember unlike dev environment, Test and Prod Node are running in container)

Tip & Star

😄 Consider star or tipping me if you found this template helpful, and wish to see more rapid development.

BTC: 1KbpCqzZ6FSfoi1R9obGEVXRHpbJMQQCda
ETH: 0x4DfD790D98F8f3E013E70da51E70B60b953c7e61
LTC: LXVYLpe9zQ48aGCuBqjLW8xxaBfVBauXST
XRP: rnftUYRq91TBL6ceK5y3UnFiYBLQMFkZn6
ADA: Ae2tdPwUPEYxapgJjg9qpg1RhyfBq5vx6ZdWXafNqZihg4rCD7baXhMf7CH
BNB: 0x4DfD790D98F8f3E013E70da51E70B60b953c7e61
PayPal

Acknowledgement

This project is inspired by the authors of existing related project

• graphql-boilerplate

• create-next-app

MISC

🌟 this project generator was bootstrapped with create-npm-create packageception