5629223407
[With next 11 requiring react 17](https://nextjs.org/blog/next-11#upgrade-guide), most of the examples need to be updated, so the following snippet updated all the examples to a compatible react version. ```bash cd examples/ fd -g 'package.json' | xargs sed -r -i 's/"react": ".*"/"react": "^17.0.2"/ fd -g 'package.json' | xargs sed -r -i 's/"react-dom": ".*"/"react-dom": "^17.0.2"/' # exclude experimental react version git checkout with-reason-relay/package.json ``` |
||
|---|---|---|
| .. | ||
| pages | ||
| public | ||
| styles | ||
| .env.local.example | ||
| package.json | ||
| README.md | ||
Deta Base Example
An example using Deta Base in a Next.js project.
Deploy your own
Once you have access to the environment variables you'll need, deploy the example using Vercel:
How to use
Execute create-next-app with npm or Yarn to bootstrap the example:
npx create-next-app --example with-deta-base with-deta-base-app
# or
yarn create next-app --example with-deta-base with-deta-base-app
Configuration
Step 1. Create a Deta Account
Create an account on Deta. Save the default Project Key which will be auto-generated on account creation.
Step 2. Setting Up Environment Variables
Copy the .env.local.example file from this directory to .env.local (which will be ignored by Git):
cp .env.local.example .env.local
Then set each variable on .env.local:
DETA_PROJECT_KEYshould be the default Project Key that you saved from step 1.
The resulting env.local file should look like this:
DETA_PROJECT_KEY=...
Step 3. Run Next.js in development mode
npm install
npm run dev
# or
yarn install
yarn dev
Your todo app should be up and running on http://localhost:3000! If it doesn't work, post on GitHub discussions.
Step 4. Deploy on Vercel
You can deploy this app to the cloud with Vercel (Documentation).
Deploy Your Local Project
To deploy your local project to Vercel, push it to GitHub/GitLab/Bitbucket and import to Vercel.
Important: When you import your project on Vercel, make sure to click on Environment Variables and set them to match your .env.local file.
Deploy from Our Template
Alternatively, you can deploy using our template by clicking on the Deploy button below.