Overview of configuration options for the Nette Application.
application: # shows "Nette Application" panel in Tracy BlueScreen? debugger: ... # (bool) defaults to true # will error-presenter be called on error? catchExceptions: ... # (bool) defaults to true in production mode # name of error-presenter errorPresenter: Error # (string) defaults to 'Nette:Error' # defines the rules for resolving the presenter name to a class mapping: ... # do bad links generate warnings? # has effect only in developer mode silentLinks: ... # (bool) defaults to false
Because error-presenters are not called by default in development mode and the errors are displayed by Tracy, changing the
true helps to verify that error-presenters works correct during
silentLinks determines how Nette behaves in developer mode when link generation fails (for example, because
there is no presenter, etc). The default value
false means that Nette triggers
true suppresses this error message. In a production environment,
E_USER_WARNING is always invoked. We
can also influence this behavior by setting the presenter variable $invalidLinkMode.
The mapping defines the rules by which the class name is derived from the presenter name.
Automatic Registration of Presenters
Nette automatically adds presenters as services to the DI container, which significantly speeds up their creation. How Nette finds out presenters can be configured:
application: # to look for presenters in Composer class map? scanComposer: ... # (bool) defaults to true # a mask that must match the class and file name scanFilter: ... # (string) defaults to '*Presenter' # in which directories to look for presenters? scanDirs: # (string|false) defaults to '%appDir%' - %vendorDir%/mymodule
The directories listed in
scanDirs do not override the default value
%appDir%, but complement it, so
scanDirs will contain both paths
%vendorDir%/mymodule. If we want to overwrite
the default directory, we use exclamation
application: scanDirs!: - %vendorDir%/mymodule
Directory scanning can be turned off by setting false. We do not recommend completely suppressing the automatic addition of presenters, otherwise application performance will be reduced.
This setting globally affects the behavior of Latte in components and presenters.
latte: # shows Latte panel in the Tracy Bar for the main template (true) or for all components (all)? debugger: ... # (true|false|'all') defaults to true # generates templates with declare(strict_types=1) strictTypes: ... # (bool) defaults to false # enables [strict parser mode |latte:develop#strict mode] strictParsing: ... # (bool) default is false # enables [checking generated code |latte:develop#Checking Generated Code] phpLinter: ... # (string) default is null # class of $this->template templateClass: App\MyTemplateClass # defaults to Nette\Bridges\ApplicationLatte\DefaultTemplate
If you are using Latte version 3, you can add new extension using:
latte: extensions: - Latte\Essential\TranslatorExtension
If you are using Latte version 2, you can register new tags either by entering the class name or by referring to the service.
install() is called by default, but this can be changed by specifying the name of another method:
latte: # registration of user Latte tags macros: - App\MyLatteMacros::register # static method, classname or callable - @App\MyLatteMacrosFactory # service with install method - @App\MyLatteMacrosFactory::register # service with register method services: - App\MyLatteMacrosFactory
routing: # shows routing panel in Tracy Bar? debugger: ... # (bool) defaults to true # to serialize router to DI container? cache: ... # (bool) defaults to false
Router is usually defined in the RouterFactory
class. Alternatively, routs can also be defined in the configuration using
mask: action pairs, but this method does
not offer such a wide variation in settings:
routing: routes: 'detail/<id>': Admin:Home:default '<presenter>/<action>': Front:Home:default
Creating PHP constants.
constants: Foobar: 'baz'
Foobar constant will created after startup.
Constants should not serve as globally available variables. To pass values to objects, use dependency injection.
You can set PHP directives. An overview of all directives can be found at php.net.
php: date.timezone: Europe/Prague
These services are added to the DI container:
||Nette\Application\Application||full application launcher|