rsnext/examples/blog-with-comment
Karl Horky 3ad55721d1
Remove incorrect entries for pnpm debug log (#47241)
**Reasons for making this change:**

- it is contained within `node_modules/`, which is already ignored
- the previous versions, which were not in `node_modules/`, did not have
a period at the beginning of the filename

Links to documentation supporting these rule changes:

**Changelog with proof here:**


ba4b2db1f2/pnpm/CHANGELOG.md (L3330)

History:

- my PR to remove this from `github/gitignore` here:
https://github.com/github/gitignore/pull/4250
- First introduced in `github/gitignore` in
https://github.com/github/gitignore/pull/3732 by `@sakurayang` (merged
by `@martinwoodward`)

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation or adding/fixing Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md



## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

---------

Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-03-26 22:26:05 -07:00
..
_posts Example blog with comments (#24829) 2021-06-10 21:04:33 -05:00
components example fix url (#42695) 2022-11-09 12:51:22 -06:00
hooks example fix url (#42695) 2022-11-09 12:51:22 -06:00
interfaces Convert many examples to TypeScript (#41825) 2022-10-26 20:28:55 +00:00
lib example fix url (#42695) 2022-11-09 12:51:22 -06:00
pages example fix url (#42695) 2022-11-09 12:51:22 -06:00
public Example blog with comments (#24829) 2021-06-10 21:04:33 -05:00
.env.local.example Example blog with comments (#24829) 2021-06-10 21:04:33 -05:00
.gitignore Remove incorrect entries for pnpm debug log (#47241) 2023-03-26 22:26:05 -07:00
environment.d.ts Convert many examples to TypeScript (#41825) 2022-10-26 20:28:55 +00:00
next-env.d.ts Remove incorrect entries for pnpm debug log (#47241) 2023-03-26 22:26:05 -07:00
package.json examples: Bump SWR to v2.0.0 (#44790) 2023-01-12 09:36:29 -08:00
postcss.config.js Example blog with comments (#24829) 2021-06-10 21:04:33 -05:00
README.md Fixed typo and error when using Auth0 service; (#27383) 2021-07-21 22:21:36 -05:00
tailwind.config.js Convert many examples to TypeScript (#41825) 2022-10-26 20:28:55 +00:00
tsconfig.json Convert many examples to TypeScript (#41825) 2022-10-26 20:28:55 +00:00

Blog with Comment

This project adds commenting functionality to Next.js blog application using Upstash and Auth0.

The comment box requires Auth0 authentication for users to add new comments. A user can delete their own comment. Also admin user can delete any comment.

Comments are stored in Serverless Redis (Upstash).

Demo

https://blog-with-comment.vercel.app/

1 Project set up

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

npx create-next-app --example blog-with-comment blog-with-comment-app

2 Set up environment variables

Copy the .env.local.example file in this directory to .env.local (which will be ignored by Git):

cp .env.local.example .env.local

3 Configuring Upstash

Go to the Upstash Console and create a new database

Upstash environment

  • REDIS_URL: Find the URL in the database details page in Upstash Console clicking on Redis Connect button.

4 Configuring Auth0

  1. Go to the Auth0 dashboard and create a new application of type Single Page Web Applications.
  2. Go to the settings page of the application
  3. Configure the following settings:
    • Allowed Callback URLs: Should be set to http://localhost:3000/ when testing locally or typically to https://myapp.com/ when deploying your application.
    • Allowed Logout URLs: Should be set to http://localhost:3000/ when testing locally or typically to https://myapp.com/ when deploying your application.
    • Allowed Web Origins: Should be set to http://localhost:3000 when testing locally or typically to https://myapp.com/ when deploying your application.
  4. Save the settings.

Auth0 environment

  • NEXT_PUBLIC_AUTH0_DOMAIN: Can be found in the Auth0 dashboard under settings.
  • NEXT_PUBLIC_AUTH0_CLIENT_ID: Can be found in the Auth0 dashboard under settings.
  • NEXT_PUBLIC_AUTH0_ADMIN_EMAIL: This is the email of the admin user which you use while signing in Auth0. Admin is able to delete any comment.

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.