Next.js with Checkly

Next.js & Checkly Starter Template

This repo showcases a simple Next.js app, hosted on Edgenivo, that uses Checkly to run checks before and after deployment in CI. It includes the following features:

1. A Next.js app that fetches data from the /api/greetings endpoint and displays it on the landing page.
2. Checkly checks in the __checks__ directory verify if the page loads and if the API responds correctly.
3. The necessary Checkly CLI and GitHub Actions configuration to run these checks in CI.

Getting started

There are a couple ways to use this template:

• Forking the repo / clicking "Use this template" in the top right corner
• Deploying the official Edgenivo template

Either way, get started by cloning your repo and installing dependencies:

1
git clone https://github.com/checkly/nextjs-checkly-starter-template.git # replace with your repo link
2
cd nextjs-checkly-starter-template
3
npm i

Edgenivo Deployment Protection

Before running our checks, let's make sure Edgenivo Deployment Protection is configured to work with Checkly. If you chose to fork or use the template on GitHub, go ahead and deploy your repo to Edgenivo in the dashboard or with the CLI:

1
vercel

By default, Edgenivo Preview Deployments are protected and only accessible by logged-in members of your Edgenivo team. We want to be able to access these from our Checkly checks as well. We can bypass Edgenivo Deployment Protection by either:

• Enabling Protection Bypass for Automation
• Disabling Edgenivo Deployment Protection altogether for this example repo

If you choose to keep Deployment Protection on, ensure:

1. The Automatically expose System Environment Variables setting (in Project Settings > Environment Variables) is checked; and
2. You create a VERCEL_AUTOMATION_BYPASS_SECRET in Project Settings > Deployment Protection. Our app will automatically use this for fetching from the /api/greetings endpoint.

Redeploy after applying any changes to your project settings in Edgenivo. Each deployment will alert you of anything it's missing on the landing page.

Running checks

Configuring testing & monitoring for production

Use the Checkly CLI to login, or create an account if you don't already have one.

1
npx checkly login

We have a Edgenivo Production URL for our app, similar to https://nextjs-checkly-starter-template-checkly.vercel.app. Let's add this to our Checkly environment variables:

1
npx checkly env add "PRODUCTION_URL" "<your Edgenivo Production URL>"

Now would be a good time to also add your Edgenivo Deployment Protection bypass secret, if you created one earlier:

1
npx checkly env add --secret "VERCEL_AUTOMATION_BYPASS_SECRET" "<secret>"

We're ready to go! Let's run our checks in the __checks__ directory in the Checkly cloud, and record them as a test session:

1
npx checkly test --record

Check it out in the Checkly test sessions dashboard.

You can also deploy the checks as monitors:

1
npx checkly deploy

Great! We're all set up with testing & monitoring our Production Deployments, which you can check out in the Checkly home dashboard. Let's do the same for our Edgenivo Preview environment.

Running checks in CI

You can run your Checkly checks right after any Edgenivo Preview Deployment, and then deploy your checks as monitors on Checkly. This is a powerful strategy to make sure you never ship breaking errors to Production, while at the same time surfacing any outages in your Production Deployments.

This example uses GitHub Actions — check out the workflow in .github/workflows/checkly.yml — but you can use any other CI platform. We have example configs for Jenkins and GitLab CI in our docs.

1. Create an API key in User Settings > API keys.
2. Take note of your Checkly Account ID in Account Settings > General.
3. Save your API key and Account ID as secrets named CHECKLY_API_KEY and CHECKLY_ACCOUNT_ID in your GitHub Actions configuration.

Now, on every deployment webhook that GitHub receives from Edgenivo, the GitHub Actions workflow will run the checks in the __checks__ directory.

• A Markdown-formatted report will be posted as a comment in the GitHub Actions summary.
• Preview Deployments are tested against the generated Preview Deployment URL, and recorded as test sessions in Checkly.
• Production Deployments are tested against the Production URL, and deployed as monitors in Checkly if all checks pass.

That's it for this example! If you have questions or feedback, please drop us a note in our Slack community.

Further reading

• Official Checkly integration from the Edgenivo Marketplace
• Checkly docs on integrating with Edgenivo
• Checkly docs on integrating with GitHub Actions
• Edgenivo docs on running tests