File: control

package info (click to toggle)
libvmod-redis 21.0%2B20250505-2
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 860 kB
  • sloc: ansic: 4,445; sh: 279; makefile: 55; ruby: 36
file content (51 lines) | stat: -rw-r--r-- 2,057 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
Source: libvmod-redis
Maintainer: Varnish Package Maintainers <team+varnish-team@tracker.debian.org>
Uploaders:
 Michael Fladischer <fladi@debian.org>,
 Marco d'Itri <md@linux.it>,
Section: web
Priority: optional
Build-Depends:
 autoconf-archive,
 debhelper-compat (= 13),
 libev-dev,
 libhiredis-dev,
 libssl-dev,
 libvarnishapi-dev (>= 7.6.0-2~),
 pkgconf,
 python3-docutils,
 redis,
Standards-Version: 4.7.2.0
Vcs-Browser: https://salsa.debian.org/varnish-team/libvmod-redis
Vcs-Git: https://salsa.debian.org/varnish-team/libvmod-redis.git
Homepage: https://github.com/carlosabalde/libvmod-redis/
Rules-Requires-Root: no

Package: varnish-redis
Architecture: any
Depends:
 ${misc:Depends},
 ${shlibs:Depends},
Multi-Arch: same
Description: access Redis servers from VCL
 VMOD using the synchronous hiredis library API to access Redis servers from
 VCL.
 .
 Highlights:
  * Full support for execution of Lua scripts (i.e. EVAL command), including
    optimistic automatic execution of EVALSHA commands.
  * All Redis reply data types are supported, including partial support to
    access to components of simple (i.e. not nested) array replies.
  * Redis pipelines are not (and won't be) supported. Lua scripting, which is
    fully supported by the VMOD, it's a much more flexible alternative to
    pipelines for atomic execution and minimizing latency. Pipelines are hard
    to use and error prone, specially when using the WATCH command.
  * Support for classic Redis deployments using multiple replicated Redis
    servers and for clustered deployments based on Redis Cluster.
  * Support for multiple databases and multiple Redis connections, local to
    each Varnish worker thread, or shared using one or more pools.
  * Support for smart command execution, selecting the destination server
    according with the preferred role (i.e. master or slave) and with distance
    and healthiness metrics collected during execution.
  * Support for Redis Sentinel, allowing automatic discovery of sick / healthy
    servers and changes in their roles.