The Complete Strapi™ Course with Plugins and Deployment - Environment Configurations

The video tutorial explains how to manage Strappy configuration files when introducing new environments, such as production. It discusses the use of environment variables for configuration differentiation and highlights Strappy's recommended practices for managing configurations. The tutorial emphasizes creating environment-specific configuration files that override or add properties to the base configuration, simplifying the process by only modifying necessary files. This approach is efficient and maintainable, especially when dealing with multiple environments like production and staging.

Why might using environment variables for configuration differentiation become less readable?

• They require additional software to manage.

• They cannot be used with Strappy.

• They are not supported by all operating systems.

• They become complex with more than two environments.

What is the advantage of using subfolders for environment configurations in Strappy?

• They increase the speed of the application.

• They enable specific configurations to override base settings.

• They reduce the need for a database.

• They allow for automatic updates.

How does Strappy handle properties not overridden in environment-specific files?

• They are duplicated.

• They are used as a fallback.

• They are deleted.

• They are ignored.

What is the first step in implementing environment configurations in Strappy?

• Creating a new database.

• Setting up a new server.

• Installing additional plugins.

• Creating a new folder for the environment.

Which modules are mentioned for configuration tweaking in the production environment?

• Admin panel, security, and user interface

• Database, security, and user interface

• User interface, server, and security

• Database, server, and admin panel