ruby-actionpack-page-caching 1.2.2-1 source package in Ubuntu
Changelog
ruby-actionpack-page-caching (1.2.2-1) unstable; urgency=medium
* Team upload
[ Utkarsh Gupta ]
* Add salsa-ci.yml
[ Debian Janitor ]
* Trim trailing whitespace.
* Use secure copyright file specification URI.
* Bump debhelper from old 11 to 12.
* Set debhelper-compat version in Build-Depends.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
[ Sruthi Chandran ]
* New upstream version 1.2.2 (Closes: #962325)
* Bump Standards-Version to 4.5.0 (no changes needed)
-- Sruthi Chandran <email address hidden> Wed, 10 Jun 2020 15:38:44 +0530
Upload details
- Uploaded by:
- Debian Ruby Extras Maintainers
- Uploaded to:
- Sid
- Original maintainer:
- Debian Ruby Extras Maintainers
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section |
|---|
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| ruby-actionpack-page-caching_1.2.2-1.dsc | 2.1 KiB | 7ecce32a1111d8d3387aa8a3e13dfad088693b372bf522f9d9fa87c1d0309093 |
| ruby-actionpack-page-caching_1.2.2.orig.tar.gz | 12.5 KiB | 46da57872e1c9f1be5118a2d9238c564edf69e6b37224c92aaaeaba727e93a65 |
| ruby-actionpack-page-caching_1.2.2-1.debian.tar.xz | 3.5 KiB | 2644f1cd8462cd532c699562484b8a5329c74d810ef4d63cda9ba7507d28aab1 |
Available diffs
- diff from 1.1.0-1 to 1.2.2-1 (8.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.
