The project was deployed on Prisma Cloud.. You can setup your instance of Prisma Cloud for free. Follow the instructions to create the account and a service. For the purpose of this demo, it doesn't matter what database or location you choose.
Install the Prisma CLI on your computer.
Please note that we will be using a environment variable to setup the Prisma secret (see Using variables in prisma.yml. Add an environment variable called PRISMA_SECRET. It can be whatever string you want.
Then open the terminal in ./server/ and run:
prisma deployThis will create the service and database on Prisma Cloud and it will populate the days collection using the seed option in prisma.yml and the default data in seed.zip (check here for more information).
Copy the Prisma endpoint from the service interface and paste it as the endpoint value in server/prisma.yml. If the pasted value contains a header query parameter, you must remove it.
Rename .env-sample to just .env and past the same endpoint value in REACT_APP_PRISMA_URL. You can get the bearer value simply by running prisma token from the ./server folder. Paste it in REACT_APP_PRISMA_BEARER.
Now, from the root folder of the project run:
npm install
npm startThis should do it. If you have problems setting it up, please open a Github or ping me on Twitter. I am @EFeliziani.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify