In this section, we will cover how to setup the cache and the system for the production environment.


The application object $app is cached when the context specified in the boot file starts withprod-or stage-. (Prod is a production site actually operated and stage is a prod mirror site.)

$context = 'prod-app';
require dirname(dirname(__DIR__)) . '/bootstrap/bootstrap.php';

Refresh $app


In production, You need to regenerate $app cache in each deploy.

To regenerate the $app cache, restart the web server (recommended).

If you do not have the authority to do so, You can recreate $app cache by changing the timestamp of the src/ directory. The BEAR.Sunday framework recognise it, then it re-generate $app and whole DI/AOP files under tmp/ directory.


Set ProdModule for the application in src/Module/ProdModule.php to customize the bindings for production and to allow HTTP OPTIONS methods.

namespace Polidog\Todo\Module;

use BEAR\Package\Context\ProdModule as PackageProdModule;
use BEAR\QueryRepository\CacheVersionModule;
use BEAR\Resource\Module\OptionsMethodModule;
use Ray\Di\AbstractModule;

class ProdModule extends AbstractModule
     * {@inheritdoc}
    protected function configure()
        $this->install(new PackageProdModule);       // default setting (recommended)
        $this->install(new OptionsMethodModule);     // Enable HTTP OPTIONS method in production
        $this->install(new CacheVersionModule('1')); // Specify version number of resource cache


There are two kinds of caches: a local cache that does not share between multiple Web servers and a shared cache that shares. The local cache is used for unchanged cachesafter deploy, such as annotations. The shared cache is used to store the resource state.

Both caches are by default chain cache of [APCu + file cache]. APCu is used preferentially and the write is done to both storages.

Resource Cache

In order to configure multiple web servers, it is necessary to set shared cache storage. Install ([Memcached] ( or [Redis] ( module.


namespace BEAR\HelloWorld\Module;

use BEAR\QueryRepository\StorageMemcachedModule;
use BEAR\Package\Context\ProdModule as PackageProdModule;
use Ray\Di\AbstractModule;
use Ray\Di\Scope;

class ProdModule extends AbstractModule
     * {@inheritdoc}
    protected function configure()
        // memcache
        // {host}:{port}:{weight},...
        $memcachedServers = ',';
        $this->install(new StorageMemcachedModule(memcachedServers);

        // Install default ProdModule
        $this->install(new PackageProdModule);


// redis
$redisServer = 'localhost:6379'; // {host}:{port}
$this->install(new StorageRedisModule($redisServer);

When using storage other than the above, create a new module with reference to each module.

Set cache expiration (TTL)

To change the default TTL,Install StorageExpiryModule.

// Cache time
$short = 60;
$medium = 3600;
$long = 24 * 3600;
$this->install(new StorageExpiryModule($short, $medium, $long);

Specify the cache version

Resource cache incompatibility is lost In the case of deploy, change the cache version.

$this->install(new CacheVersionModule($cacheVersion));

If you want to destroy the resource cache every time you deploy, assign time and random value to $ cacheVersion. (This statement is invoked only once after deploy.)

HTTP Cache

The resource annotated with the @Cacheable, outputs an ETag entity tag.

By using this ETag, we can return a 304 (Not Modified) appropriate response when the resource is not modified.

(Therefore, we can save not only the cpu cost but also the network transfer cost.)


To use HttpCache in a script, we are going to inject HttpCache using HttpCacheInject trait in App class.

namespace MyVendor\MyApi\Module;

use BEAR\QueryRepository\HttpCacheInject; // Add this line
use BEAR\Sunday\Extension\Application\AbstractApp;
use Ray\Di\Di\Inject;

class App extends AbstractApp
    use HttpCacheInject; // Add this line


Next, modify the route section in bootstrap/bootstrap.php to return a 304 when the contents are not modified, by adding an if conditional statement.

route: {
    $app = (new Bootstrap)->getApp(__NAMESPACE__, $context);
    if ($app->httpCache->isNotModified($_SERVER)) {

ETag is also updated automatically, but you need to specify the relation of the resource caches using @Refresh and @Purge annotations.


⚠️ Avoid overwriting updates

Overwriting a running project folder with rsync or the like has a risk of inconsistency between the resource cache and automatic generation class file created in tmp/ and the actual class. On heavily loaded sites, it is possible that multiple jobs such as cache creation and opcode creation are executed at the same time, exceeding the performance capacity of the site.

Set up in a different directory and switch it (by symlink) if the setup is OK.

When setting up, you can warm up the project using the vendor/bin/bear.compile script. The compilation script prepares all static cache files such as dynamically created files and annotations for DI / AOP in advance.

Since injection is done in all classes, there is no problem of DI error at runtime. In addition, although .env generally contains credential information such as API key and password, all contents are imported into PHP file and can be deleted after compilation. Compilation makes the deployment faster and safer.

Execution at the console

vendor/bin/bear.compile 'Polidog\Todo' prod-html-app /path/to/prject

Deployer’s BEAR.Sunday recipe is convenient and safe to use. Consider using the other server configuration tool as well as referring or running the Deployer script. Since Deployer generates a project directory each time, you do not have to worry about regenerating $app.