Download the PHP package jelix/php-redis-plugin without Composer
On this page you can find all versions of the php package jelix/php-redis-plugin. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
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 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.
Informations about the package php-redis-plugin
Plugins for Jelix to access to Redis through jKVDb (the nosql API of Jelix) and jCache.
These plugins are using the library php-redis, a pure PHP library to connect to Redis.
You may want to use these plugins if you cannot use Redis plugins provided into Jelix 1.7+, that use the API of the Redis extension.
These plugins are for Jelix 1.7.x and higher. See the jelix/jelix repository to see their history before Jelix 1.7.
installation
Install it by hands like any other Jelix plugins, or use Composer if you installed Jelix 1.7+ with Composer.
In your project:
You can use the plugins. There name is "redis_php".
configuration
For the configuration, indicate a and a parameter in the profiles.ini.php file. The parameter is optional (default is 0) and should indicate the number of the database to use into Redis.
Example of profiles:
This driver supports the interface.
Other parameter configuration:
key_prefix: indicate a name in it, and all keys will be prepend by this namekey_prefix_flush_method: when a key_prefix is set, indicates how the flush should be made, as deletion can be very expensive in resources. Possible values aredirect: keys are directly deleted, one after one. Warning: this can be very time expensive. Use it only if you know you are using only few keys.jcacheredisworkerfor a jCache profile, orjkvdbredisworkerfor a jKvDb driver: It pushes the prefix into a 'list' value in Redis. Keys then should be delete by an other process/worker. Such worker is provided in jelix (see lib/jelix/core-modules/jelix/controllers/redisworker.cmdline.php)event: a jelix event is notified (jCacheRedisFlushKeyPrefixfor jCache, orjKvDbRedisFlushKeyPrefixfor jKvDb). Up to you to create a listener that will delete the keys in the manner you want. Event parameters:prefixindicates the prefix of keys to delete,profileindicate the jCache/jKvdb to use for the connection.
unit tests
Unit tests are in Testapp, in the jelix/jelix repository.
