The deployment instructions are specifically for Vercel. If you are deploying on other platforms, you need to adapt the instructions for running the project locally.
To deploy this project on Vercel, you will need:
- Vercel Account
- Access to a Couchbase Capella database running the Query Service. Alternatively, you have the option to sign up for a free Capella database in the integration flow.
- If you are connecting to an existing Capella account, create a bucket called
user_profile, and a collection calledprofile(within the_defaultscope).- Note: the
buildstep will attempt to create the collection and load the sample data within yourCB_BUCKETon deployment.
- Note: the
- Click Deploy
- Follow the steps when prompted. The integration step will open the Couchbase Capella UI and allow you to select resources to connect.
- Explore the newly deployed application: create, update, and delete some user profiles. A few sample profiles will be added automatically, and you can load the sample data manually by following these instructions.
- Infinite Loading State OR
Query failed: bucket not foundORQuery failed: parsing error- No data received from the database. Be sure you are using the right bucket in your
CB_BUCKETenvironment variable, a_defaultscope, and a collection namedprofile.
- No data received from the database. Be sure you are using the right bucket in your
- 504 Gateway Timeout after deploying
- This error usually occurs when the application cannot reach the database. Ensure that the environment variables are correct, IP addresses are allowed, and the Database User credentials match those in the environment variables.
- Check to ensure your Database wasn't deleted.
https://couchbase-nextjs-quickstart.vercel.app/
To run this project locally, you will need:
- A Couchbase Capella database or Couchbase 7+ database running locally
- Node.js & NPM
- Next.js
- Code Editor
Clone the source code:
git clone https://github.com/couchbase-examples/nextjs-quickstart.gitInstall required dependencies:
npm installIf you are using Capella, you'll have to manually create a bucket named user_profile and a collection named profile. See the documentation on managing buckets and creating a collection for more information. Note that this collection should be created on the _default scope.
We've included a .env.local.example file with blank values for you to copy into a file called .env.local and fill in the values. We've also included a .env.default file for testing and running in GitPod. In most cases, you can ignore the default config file.
CB_USERNAME- The username of an authorized user on your database. Follow these instructions to create database credentials on Capella.CB_PASSWORD- The password that corresponds to the user specified above.CB_CONNECT_STRING- The Couchbase connection string. Use the connection string specified on the 'Connect' tab within Capella (formatted likecouchbases://cb.<xxxxxx>.cloud.couchbase.com) orcouchbase://localhostfor a local/Docker database.CB_BUCKET- The bucket you'd like to connect to. Set this touser_profilesfor this template.
If you have Couchbase running locally, we can create the bucket and collection by running the following command:
npm run init-db:localIf you'd like to add the sample data, run:
npm run load-sample-dataNote: this will also attempt to create a profile collection.
Extra Step for Capella Databases: if you've manually set up your bucket and collection, you'll need to create the necessary indices as well. To accomplish this, run:
npm run build-indexesThis is because the index creation code is contained within the database initialization script, which we don't use for Capella databases.
Now we're ready to run our application:
npm run devIf everything is configured properly, you should be able to navigate to localhost:3000 to see the example application. For troubleshooting and additional setup instructions please refer to the NextJS_README.md included in the with-couchbase starter.
- We've included a
MOCK_DATA.jsonfile containing 15 documents with various mocked user data. Thebuildstep will automatically load the sample data, but you may want to also load it manually for local testing. Usenpm run load-sample-datato insert the documents to your database. Be sure your local environment variables are set correctly! - This file can also be imported into Capella manually.
- You can also add your own profile data to the database manually by clicking the + icon in the UI.
- We've included a
.env.defaultfile which is used for testing and gitpod instances of the project to ensure smooth setup in these environments. - The build step is set up to not set a specific
.envfile and instead use the variables in the system environment. This is to ensure that the application can be deployed to Vercel properly, but can cause issues when trying to build locally.- If you need to pass in an environment file, you can adjust the build script to use the scripts that are not postfixed with
:no-envin package.json.
- If you need to pass in an environment file, you can adjust the build script to use the scripts that are not postfixed with
- In the completed quickstart code, fetch URLs use a dynamic
originvariable instead of hard codinghttp://localhost:3000to ensure requests work when running in other environments. - NOTE FOR CAPELLA DATABASES: The database initialization code currently only works with local databases. If you are using Capella, you'll need to manually create a bucket called
user_profileand then within that buckets default scope, a collection calledprofile. See here for more info on managing buckets in Capella.. After bucket and collection creation, you can use the index creation command:npm run build-indexes. Runningnpm run init-db:localwill also work to create the required indices. The bucket and collection creation steps will fail withECONNREFUSEDbut it will still be able to create the index on your Capella database.
A suite of integration tests has been included, and can be run by first setting up the database:
npm run init-db:default
and then using the npm test command.
