rsnext/examples/with-edgedb
Steven 4466ba436b
chore(examples): use default prettier for examples/templates (#60530)
## Description
This PR ensures that the default prettier config is used for examples
and templates.

This config is compatible with `prettier@3` as well (upgrading prettier
is bigger change that can be a future PR).

## Changes
- Updated `.prettierrc.json` in root with `"trailingComma": "es5"` (will
be needed upgrading to prettier@3)
- Added `examples/.prettierrc.json` with default config (this will
change every example)
- Added `packages/create-next-app/templates/.prettierrc.json` with
default config (this will change every template)

## Related

- Fixes #54402
- Closes #54409
2024-01-11 16:01:44 -07:00
..
components chore(examples): use default prettier for examples/templates (#60530) 2024-01-11 16:01:44 -07:00
dbschema Add with-edgedb example (#35929) 2022-04-27 16:49:17 +00:00
pages chore(examples): use default prettier for examples/templates (#60530) 2024-01-11 16:01:44 -07:00
.eslintignore Add with-edgedb example (#35929) 2022-04-27 16:49:17 +00:00
.gitignore Add .yarn/install-state.gz to .gitignore (#56637) 2023-10-18 16:34:48 +00:00
client.ts chore(examples): use default prettier for examples/templates (#60530) 2024-01-11 16:01:44 -07:00
edgedb.toml Update edgedb.toml (#39243) 2022-08-02 02:31:04 +00:00
next-env.d.ts Remove incorrect entries for pnpm debug log (#47241) 2023-03-26 22:26:05 -07:00
package.json Add with-edgedb example (#35929) 2022-04-27 16:49:17 +00:00
README.md chore(examples): use default prettier for examples/templates (#60530) 2024-01-11 16:01:44 -07:00
seed.ts chore(examples): use default prettier for examples/templates (#60530) 2024-01-11 16:01:44 -07:00
tsconfig.json Add with-edgedb example (#35929) 2022-04-27 16:49:17 +00:00

Full-stack EdgeDB + Next.js application

A simple blog application built with Next.js, TypeScript, React, and EdgeDB on the backend.

Deploy your own

Deploy the example using Vercel:

Deploy with Vercel

How to use

Download the example project

Execute create-next-app with npm, Yarn, or pnpm to bootstrap the example:

npx create-next-app --example with-edgedb with-edgedb-app
yarn create next-app --example with-edgedb with-edgedb-app
pnpm create next-app --example with-edgedb with-edgedb-app

Then cd into the created directory.

$ cd with-edgedb-app

Install the CLI

First install the EdgeDB CLI if you haven't already.

# macOS/Linux
$ curl --proto '=https' --tlsv1.2 -sSf https://sh.edgedb.com | sh

# Windows (Powershell)
$ iwr https://ps1.edgedb.com -useb | iex

Initialize the EdgeDB project

Initialize the project with the following CLI command:

$ edgedb project init

After you follow the prompts, this command will spin up a local EdgeDB instance and apply all the migrations inside dbschema/migrations. Now that the project is initialized, all EdgeDB clients initialized inside the project directory will connect to this instance automatically—no need for environment variables or hard-coded configuration. (Read more about projects here.)

Install dependencies

Install npm dependencies:

$  npm install
# or
$  yarn

Generate the query builder

This project uses the EdgeQL query builder for TypeScript. This tool can express any EdgeQL query in a code-first way and infers a static return type. Generate it with the following command:

$ npx edgeql-js

The query builder consists of several files that are generated into the dbschema/edgeql-js directory. Import it like so:

import e from "./dbschema/edgeql-js";

Seed the database

$ npx ts-node seed.ts

Start the app

$ yarn dev

The application should now be running on http://localhost:3000.

Notes

packages structure

  • /: See all published posts
  • /drafts: See all drafts
  • /create: Form to create new draft
  • /blog/:id: See either an edit page or a published post, depending on the publish status of the post.

API structure

  • POST /api/post: Create a new post
    • Body: {title: string; content: string; authorName: string}
  • PATCH /api/post/:id: Update a post by id
    • Body: {title?: string; content?: string;}
  • PUT /api/publish/:id: Publish a post by id
  • DELETE /api/post/:id: Delete a post by id

Evolving the app

Evolving the application typically requires three steps:

  1. Update the schema in dbschema/default.esdl
  2. Generate a new migration with edgedb migration create
  3. Apply the migration with edgedb migrate
  4. Regenerate the query builder with npx edgeql-js
  5. Update the application code, as needed.

Deployment

To deploy this application, deploy EdgeDB to your preferred cloud provider:

Then:

  1. Find your instance's DSN (AKA connection string). The exact instructions for this depend on which cloud you are deploying to.

  2. Use this DSN to migrate your remote instance to the latest schema. Run this command from inside your project directory.

edgedb migrate --dsn <your-instance-dsn> --tls-security insecure

You have to disable TLS checks with --tls-security insecure. All EdgeDB instances use TLS by default, but configuring it is out of scope of this project.

  1. Deploy this app to Vercel with the button above. You'll be prompted to provide a value for EDGEDB_DSN, the value from the previous step.

  2. Open the application at the deployment URL supplied by Vercel.

Next steps