Modules
Slick is a modular framework where nearly all features are implemented as modules. Some modules are enabled by default and cannot be disabled, while others may need to be enabled to set up their dependencies in the dependency container, console commands, HTTP middlewares, and default settings. It is always possible to override container services and settings for these modules.
What’s a module?
A module is typically a package that provides specific functionality. Whether you need to develop a web application or a command line tool, modules enable you to extend the framework’s capabilities by adding command line commands, HTTP middleware handlers, and configuring the dependency container and default settings to work with.
Available modules
You can always check witch modules are installed and witch are enabled.
bin/console modules
Here is an example of what output should be:
So, in the above output you can see what modules are available and from those what are the enebled ones.
Enable a module
Enabling a module is easy. Just run the following command with the module name you want to enable:
bin/console enable orm
In the above case, the orm module will be enabled. When a module is enabled, the system sets up all necessary files needed to use the module’s resources, such as console commands, services, HTTP middlewares, and settings. Note that this module setup occurs on every request during the bootstrap process.
Disable a module
There is also a command to disable a module.
bin/console disable orm
When disabled, a module will not be loaded during request bootstrap. As a result, all associated console commands, services, HTTP middlewares, and settings will not be loaded.