Debian Codegraph @

debian/control

raw
1 Source: lua-resty-lrucache
2 Section: net
3 Priority: optional
4 Build-Depends:
5 debhelper-compat (= 13),
6 dh-lua,
7 Maintainer: Debian Lua Team <[email protected]>
8 Uploaders:
9 Jan Mojžíš <[email protected]>,
10 Homepage: https://github.com/openresty/lua-resty-lrucache
11 Standards-Version: 4.7.2
12 Rules-Requires-Root: no
13 Vcs-Git: https://salsa.debian.org/lua-team/lua-resty-lrucache.git
14 Vcs-Browser: https://salsa.debian.org/lua-team/lua-resty-lrucache
15
16 Package: lua-resty-lrucache
17 Depends:
18 libluajit-5.1-2,
19 ${misc:Depends},
20 ${shlibs:Depends},
21 Provides:
22 ${lua:Provides},
23 Architecture: all
24 Description: Simple LRU cache for the ngx_lua module
25 The LRU cache resides completely in the Lua VM and is subject to Lua GC.
26 As such, do not expect it to get shared across the OS process boundary.
27 The upside is that you can cache arbitrary complex Lua values (such as deep
28 nested Lua tables) without the overhead of serialization (as with ngx_lua's
29 shared dictionary API). The downside is that your cache is always limited to
30 the current OS process (i.e. the current Nginx worker process). It does not
31 really make much sense to use this library in the context of init_by_lua
32 because the cache will not get shared by any of the worker processes (unless
33 you just want to "warm up" the cache with predefined items which will
34 get inherited by the workers via fork()).