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
|
Source: ruby-actionpack-page-caching
Section: ruby
Priority: optional
Maintainer: Debian Ruby Team <pkg-ruby-extras-maintainers@lists.alioth.debian.org>
Uploaders: Daniel Leidert <dleidert@debian.org>
Build-Depends: debhelper-compat (= 13),
gem2deb,
rails,
rake,
ruby-actionpack (>= 2:5.0.0),
ruby-minitest,
ruby-mocha
Standards-Version: 4.6.0
Vcs-Git: https://salsa.debian.org/ruby-team/ruby-actionpack-page-caching.git
Vcs-Browser: https://salsa.debian.org/ruby-team/ruby-actionpack-page-caching
Homepage: https://github.com/rails/actionpack-page_caching
Testsuite: autopkgtest-pkg-ruby
XS-Ruby-Versions: all
Rules-Requires-Root: no
Package: ruby-actionpack-page-caching
Architecture: all
XB-Ruby-Versions: ${ruby:Versions}
Depends: ${misc:Depends},
${ruby:Depends},
${shlibs:Depends}
Breaks: ruby-actionpack-2.3
Replaces: ruby-actionpack-2.3
Description: static page caching for Action Pack (removed from core in Rails 4.0)
Page caching is an approach to caching where the entire action output of is
stored as a HTML file that the web server can serve without going through
Action Pack.
.
This is the fastest way to cache your content as opposed to going dynamically
through the process of generating the content. Unfortunately, this incredible
speed-up is only available to stateless pages where all visitors are treated
the same. Content management systems -- including weblogs and wikis -- have
many pages that are a great fit for this approach, but account-based systems
where people log in and manipulate their own data are often less likely
candidates.
|
