Configuration

The configuration of a Strapi project lives in the /config folder:

. # root of the project
├──── config
│     ├ api.js|ts
│     ├ admin.js|ts
│     ├ cron-tasks.js|ts
│     ├ database.js|ts
│     ├ features.js|ts
│     ├ middlewares.js|ts
│     ├ plugins.js|ts
│     └ server.js|ts

The block above is an excerpt from the project structure. You can click on any file name in purple to read the corresponding documentation. Visit the project structure page for the full version.

Base configurations

From the /config folder, you can find and define the following base configurations:

Configuration topic	File path	Required or optional
Database	config/database	Required
Server	config/server	Required
Admin panel	config/admin	Required
Middlewares	config/middlewares	Required
API calls	config/api	Optional, used to define some general settings for responses and other REST-related parameters.

Additional configuration for specific features

Some specific features require additional configuration:

Feature	Location	Required or optional
Plugins	In the config/plugins file	Optional if using only built-in plugins with default presets. Required to enable, configure, or disable plugins. Can also be used to configure the Upload plugin (which handles the Media Library feature) and GraphQL.
TypeScript	In tsconfig.json for general TypeScript-related configuration In the config/typescript file for dedicated TypeScript features specific to Strapi	Required to use TypeScript efficiently
API tokens	In the config/admin file	Required if using API tokens for authentication instead of the Users & Permissions plugin
Lifecycle functions	In the /src/index file	Optionally used to perform various actions that happen during the server lifecycle. Includes the register, bootstrap, and destroy functions.
Cron jobs	In the /config/server file to enable the feature In a dedicated, optional cron-tasks file that can be used to declare the jobs	Required to setup CRON jobs for the server.
Environment variables	In dedicated files and folders for the environment (e.g., config/env/production/server)	Optionally used to define different environments and their variables.
Single Sign-On (SSO) EnterpriseThis feature is available with an Enterprise plan.	In the config/admin file	Required to use the Entreprise-only SSO feature if enabled on your project.
Feature flags	In the config/features file	Optional for a typical, stable Strapi application. Only required to enable future flags.

Guides

The following guides will help you address specific use cases related to the Strapi configuration:

How to create custom conditions for Role-Based Access Control (RBAC)

How to use public assets

How to access and cast environment variables

How to access configuration values from the code