ruby-actionpack-page-caching 1.2.4-1 source package in Ubuntu
Changelog
ruby-actionpack-page-caching (1.2.4-1) unstable; urgency=medium * New upstream release. [ Balasankar C ] * Remove Balu as an uploader. [ Debian Janitor ] * Update watch file format version to 4. * Bump debhelper from old 12 to 13. [ Daniel Leidert ] * d/control: Add Rules-Requires-Root field. (Uploaders): Add myself. (Standards-Version): Bump to 4.6.0. (Build-Depends): Add rails due to requiring rails/version. (Depends): Remove interpreters and use ${ruby:Depends}. * d/copyright: Add Upstream-Contact field. (Copyright): Add team. * d/rules: Use gem installation layout. * d/tests/control.ex: Remove template file. * d/upstream/metadata: Add missing fields. -- Daniel Leidert <email address hidden> Sun, 28 Nov 2021 23:53:01 +0100
Upload details
- Uploaded by:
- Debian Ruby Extras Maintainers
- Uploaded to:
- Sid
- Original maintainer:
- Debian Ruby Extras Maintainers
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
ruby-actionpack-page-caching_1.2.4-1.dsc | 2.2 KiB | c9d243904d2668969336dd126d5e079e42e16d862fb8dc8f42271421dcad5c09 |
ruby-actionpack-page-caching_1.2.4.orig.tar.gz | 12.9 KiB | 6a3136f00a049c2f85212cba52c2d9627a1d2e4dc30386e25a9378f42e6cb9ef |
ruby-actionpack-page-caching_1.2.4-1.debian.tar.xz | 3.4 KiB | 4e7d12426353a7169d56f78d048c925305e3b7638c7a64a17539f074764fb71a |
Available diffs
- diff from 1.2.2-1 to 1.2.4-1 (6.3 KiB)
No changes file available.
Binary packages built by this source
- ruby-actionpack-page-caching: 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.