Strapi comes with a full featured Command Line Interface (CLI) which lets you scaffold and manage your project in seconds.
Start your Strapi application with autoReload enabled. Learn more
npm run develop
# or
yarn develop
Start your Strapi application with autoReload disabled. Learn more
npm run start
# or
yarn start
Build your admin panel. Learn more
npm run build
# or
yarn build
We use CDK to deploy.
Every time you merge into develop, the CMS is deployed into our test environment.
To deploy to production, you need to run this GitHub action manually.
You can also deploy from local with make deploy development.
If during the deploy you have problems, you can stop the deploy with:
- Check status
make deploy_status development- Stop deploy
make deploy_stop development- If the status is
UPDATE_ROLLBACK_FAILED, continue with rollback
make deploy_rollback development- You can wait for the rollback to finish with
make deploy_wait developmentIf you want to add a new dev environment, you need to add a new environment in the bin/cdk.ts file, under the environmentConfigs array (you can copy test as example).
This will create a new environment in the AWS account, with the proper configuration (including RDS database, ECS...).
The first time you apply the CDK stack it will create the database, but it will not be initialized, so the creation of ECS cluster will fail.
After failing, connect to the RDS database and run the following command to create it:
CREATE DATABASE strapi
DEFAULT CHARACTER SET utf8mb4
COLLATE utf8mb4_0900_ai_ci
DEFAULT ENCRYPTION='N';Then you can run the CDK stack again and it will create the ECS cluster.
- Build the docker image
make build- Start the docker container
make start- Stop the docker container
make stop- Get diff with infrastructure changes
make diff development- Deploy infrastructure changes
make deploy developmentThe Gridly Integration plugin includes a configurable logging system to control the verbosity of log messages. This helps manage log output in different environments and during debugging.
The plugin supports four log levels (from least to most verbose):
error- Only error messages (critical failures)warn- Warnings and errorsinfo- Informational messages, warnings, and errors (default for production)debug- All messages including detailed debugging information (default for development)
The log level can be configured in two ways (in order of precedence):
Set the GRIDLY_LOG_LEVEL environment variable:
# .env file
GRIDLY_LOG_LEVEL=debug
# Or export in shell
export GRIDLY_LOG_LEVEL=infoConfigure in config/plugins.js:
"gridly-integration": {
enabled: true,
resolve: "./src/plugins/gridly-integration",
config: {
logLevel: "debug", // 'error', 'warn', 'info', or 'debug'
},
},- Production (
NODE_ENV=production): Defaults toinfolevel - Development: Defaults to
debuglevel
# Enable debug logging for troubleshooting
GRIDLY_LOG_LEVEL=debug npm run develop
# Use minimal logging (errors only) in production
GRIDLY_LOG_LEVEL=error npm run start
# Enable warnings and errors
GRIDLY_LOG_LEVEL=warn npm run developAll log messages from the Gridly Integration plugin are prefixed with [Gridly Integration] for easy identification in log files.
- Resource center - Strapi resource center.
- Strapi documentation - Official Strapi documentation.
- Strapi tutorials - List of tutorials made by the core team and the community.
- Strapi blog - Official Strapi blog containing articles made by the Strapi team and the community.
- Changelog - Find out about the Strapi product updates, new features and general improvements.
Feel free to check out the Strapi GitHub repository. Your feedback and contributions are welcome!
- Discord - Come chat with the Strapi community including the core team.
- Forum - Place to discuss, ask questions and find answers, show your Strapi project and get feedback or just talk with other Community members.
- Awesome Strapi - A curated list of awesome things related to Strapi.
🤫 Psst! Strapi is hiring.