Download the PHP package labor-digital/typo3-distributed-cache-clearing without Composer

On this page you can find all versions of the php package labor-digital/typo3-distributed-cache-clearing. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of labor-digital/typo3-distributed-cache-clearing

Informations about the package typo3-distributed-cache-clearing

TYPO3 Distributed Cache Clearing

Utility extension to clear the local file caches in a multi-container setup. It is designed to be easily extendable with all kinds of message queue backends. By default a DB/TYPO3 Registry and Redis backend are included.

Requirements

Installation

Install this package using Composer:

Usage

To utilize the distributed cache clearing you need to register a backend class using the ext config logic. This will activate the message handling when the TYPO3 cache is cleared in the backend or though the CLI.

In order to listen for the cache cleared event emitted in another container you can use multiple approaches. The first one, which is the simplest to implement is by setting the "check in every request" option to true. It is also done in the ext config class. The major downside of this option is a potential dip in your performance, especially if external event queues (SNS, ServiceBus, ...) are used.

If your infrastructure allows you to perform an HTTP request to EACH container independently, and you use the T3FA extension, you may use the DccBundle in your site routing configuration The route will be available at: /api/dcc/clearIfRequired.

Alternatively you can use the built-in cli command t3dcc:handleMessages which does the same.

As as last resort for highly specialized setups you can use the /ext/t3dcc/handleMessages.php file provided by the extension. It can be executed in ANY other PHP script, even without TYPO3 context. It contains an encapsulated bootstrap and small application to boot up the TYPO3 core and flush the caches if needed. Before you can include the file you need to set T3DCC_AUTOLOAD_PATH either as environment variable, or constant to the absolute path to your composer autoload.php. The rest should work automatically.

This script would be located in the public/typo3conf directory of your installation.

Backends

The extension provides two simple backends:

RegistryMessageBackend

This backend utilizes the TYPO3 sys_registry table to send messages between the containers. It is the most simple implementation and does not require additional options or configuration.

RedisMessageBackend

This backend utilizes a Redis database as messaging queue between containers. The configuration follows the same structure as the redis cache backend.

Postcardware

You're free to use this package, but if it makes it to your production environment, we highly appreciate you sending us a postcard from your hometown, mentioning which of our package(s) you are using.

Our address is: LABOR.digital - Fischtorplatz 21 - 55116 Mainz, Germany.

We publish all received postcards on our company website.

All versions of typo3-distributed-cache-clearing with dependencies

PHP Build Version
Package Version
Requires labor-digital/typo3-better-api Version ^10.35.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package labor-digital/typo3-distributed-cache-clearing contains the following files

Loading the files please wait ....