Configuration guide
Set Next.js environment variables
Use separate production and development values. Load and edit each environment from the project when you need to change configuration.
Identify the values your app reads
Check the repository for values such as database URLs, authentication secrets, CMS tokens, payment keys, and public site URLs.
Use the value names that the app already reads. A renamed value does not configure the application unless its code also changes.
Add production values
- 1Open the project Environment page.
- 2Choose Production.
- 3Load the environment when you need to review or edit it.
- 4Add or update each value, then save the changes.
- 5Redeploy the production app when the change requires a new build or process.
Use different development values
A project development environment has its own set of environment variables. Use development-only credentials and URLs there when the provider supports them.
Do not put a production secret in development just to make a test pass. Fix the missing development configuration instead.
Connect services that Host Little does not provide
Use environment variables to connect a database, CMS, cache, storage provider, authentication provider, or email provider that you control.
Host Little runs the Next.js app. The external provider keeps its own service limits, access controls, backups, and billing.
Check the app after a change
- 1Redeploy when the app needs a new process or build.
- 2Open the project URL and test the route that uses the changed value.
- 3Use redacted logs and the variable names in the portal to diagnose a failed deployment. Do not paste secrets into a support request.