rsnext/examples/with-apollo-neo4j-graphql
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
..
apollo [EXAMPLES] Update with-apollo-neo4j-graphql (#44570) 2023-02-23 13:37:22 +00:00
components [EXAMPLES] Update with-apollo-neo4j-graphql (#44570) 2023-02-23 13:37:22 +00:00
pages [EXAMPLES] Update with-apollo-neo4j-graphql (#44570) 2023-02-23 13:37:22 +00:00
public [ EXAMPLES ] Added with-apollo-neo4j-graphql (#16560) 2020-11-20 20:38:08 +00:00
styles [EXAMPLES] Update with-apollo-neo4j-graphql (#44570) 2023-02-23 13:37:22 +00:00
types [EXAMPLES] Update with-apollo-neo4j-graphql (#44570) 2023-02-23 13:37:22 +00:00
util [EXAMPLES] Update with-apollo-neo4j-graphql (#44570) 2023-02-23 13:37:22 +00:00
.env.local.example fix(38043): replace double slashes with hashtag for comment lines in … (#38044) 2022-06-27 00:04:05 +00:00
.gitignore Remove incorrect entries for pnpm debug log (#47241) 2023-03-26 22:26:05 -07:00
movie-sample.md [ EXAMPLES ] Added with-apollo-neo4j-graphql (#16560) 2020-11-20 20:38:08 +00:00
next-env.d.ts Remove incorrect entries for pnpm debug log (#47241) 2023-03-26 22:26:05 -07:00
next.config.js [EXAMPLES] Update with-apollo-neo4j-graphql (#44570) 2023-02-23 13:37:22 +00:00
package.json [EXAMPLES] Update with-apollo-neo4j-graphql (#44570) 2023-02-23 13:37:22 +00:00
README.md [EXAMPLES] Update with-apollo-neo4j-graphql (#44570) 2023-02-23 13:37:22 +00:00
tsconfig.json [EXAMPLES] Update with-apollo-neo4j-graphql (#44570) 2023-02-23 13:37:22 +00:00

Neo4j Example with GraphQL and Apollo

This is a simple setup for Next using Neo4j Database with GraphQL and Apollo. Neo4j's Movies dataset example is used to run the example.

Deploy your own

Once you have access to the environment variables you'll need, deploy the example using Vercel:

Deploy with Vercel

How to use

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

npx create-next-app --example with-apollo-neo4j-graphql with-apollo-neo4j-graphql-app
yarn create next-app --example with-apollo-neo4j-graphql with-apollo-neo4j-graphql-app
pnpm create next-app --example with-apollo-neo4j-graphql with-apollo-neo4j-graphql-app

Configuration

Step 1. Create a Neo4j database

First, you'll need a Neo4j database. Neo4j Desktop and Neo4j Online Sandbox are good and free-to-use options.

Step 2. Add the movie graph model to the database

This example uses a database containing Movies, you can add it like so:

:play movie-graph

Also included is a Cypher movie sample query if needed.

Step 3. Set up environment variables

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

cp .env.local.example .env.local

Then set each variable on .env.local to match your database URI and credentials.

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.

Deploy with Vercel

Notes

To learn more about how to use the Neo4j GraphQL Library, you can take a look at the documentation or check out the GitHub repository.