Play Framework configuration
Play Framework
Play Framework is our web framework of choice. It handles incoming HTTP requests . More information about the framework can be found on their public site.
Default configuration
Play framework is very configurable thus it contains many config parameters that can be used to tune it. All of the possible parameters could be found in the documentation.
Config properties that are used/changed in our applications
We override / require to override some properties:
Parameter | Description | Value |
---|---|---|
http.port | Port on which application should be listening | Depends on service |
play.http.secret.key | Application secret, unique hash | Should be overridden |
play.evolutions.autoApply | Should evolutions be auto-applied | true |
play.evolutions.useLocks | Should evolutions use locks (recommended) | true |
play.http.parser.maxMemoryBuffer | Maximum payload size that could be loaded to the memory | overridden in some services |
play.http.parser.maxDiskBuffer | Maximum payload size that can be stored on hard drive | overridden in some services |
play.server.http.idleTimeout | Time after which request will be ended | overridden in some services |
play.http.session.cookieName | Session's cookie name | __Host-session |
play.http.session.secure | Is cookie enabled only for https | true |
play.http.session.sameSite | Parameter sameSite for session's cookie | None or SameSite |
Updated over 1 year ago
What’s Next