Add documentation: Document Environment Variables in a1base-nextjs-template #14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Document Environment Variables in a1base-nextjs-template
This document outlines the required environment variables for the
a1base-nextjs-template
. Properly configuring these variables is crucial for the application to function correctly and securely.Configuration
The
a1base-nextjs-template
relies on environment variables for various configurations, including API keys, secrets, and database connection details. These variables are typically set in a.env
file in the root directory of the project or configured directly in your hosting environment (e.g., Vercel, Netlify, AWS).Important: Never commit your
.env
file to version control (e.g., Git). Add it to your.gitignore
file to prevent accidental exposure of sensitive information.Environment Variables
The following table lists the required environment variables, their purpose, example values, and instructions on how to set them.
| Variable Name | Purpose