1
0
mirror of https://git.FreeBSD.org/ports.git synced 2024-10-17 19:39:43 +00:00

databases/rubygem-solid_cache: Add rubygem-solid_cache 1.0.6

Solid Cache is a database-backed Active Support cache store that let's you keep
a much larger cache than is typically possible with traditional memory-only
Redis or Memcached stores. This is thanks to the speed of modern SSD drives,
which make the access-time penalty of using disk vs RAM insignificant for most
caching purposes. Simply put, you're now usually better off keeping a huge cache
on disk rather than a small cache in memory.
This commit is contained in:
Po-Chuan Hsieh 2024-09-18 13:51:29 +08:00
parent 88545fc618
commit 39f77ea66f
No known key found for this signature in database
GPG Key ID: 9A4BD10F002DD04B
4 changed files with 31 additions and 0 deletions

View File

@ -1043,6 +1043,7 @@
SUBDIR += rubygem-sdbm
SUBDIR += rubygem-seed-fu
SUBDIR += rubygem-solid_cable
SUBDIR += rubygem-solid_cache
SUBDIR += rubygem-sqlite3
SUBDIR += rubygem-sqlite3-ruby
SUBDIR += rubygem-sqlite31

View File

@ -0,0 +1,21 @@
PORTNAME= solid_cache
PORTVERSION= 1.0.6
CATEGORIES= databases rubygems
MASTER_SITES= RG
MAINTAINER= sunpoet@FreeBSD.org
COMMENT= Database-backed ActiveSupport::Cache::Store
WWW= https://github.com/rails/solid_cache
LICENSE= MIT
LICENSE_FILE= ${WRKSRC}/MIT-LICENSE
RUN_DEPENDS= rubygem-activejob72>=7.2:devel/rubygem-activejob72 \
rubygem-activerecord72>=7.2:databases/rubygem-activerecord72 \
rubygem-railties72>=7.2:www/rubygem-railties72
USES= gem
NO_ARCH= yes
.include <bsd.port.mk>

View File

@ -0,0 +1,3 @@
TIMESTAMP = 1726487308
SHA256 (rubygem/solid_cache-1.0.6.gem) = fe1acf73fbe4a6a53620425317949082d3b99e0cfd35416106b56220fa66c311
SIZE (rubygem/solid_cache-1.0.6.gem) = 20992

View File

@ -0,0 +1,6 @@
Solid Cache is a database-backed Active Support cache store that let's you keep
a much larger cache than is typically possible with traditional memory-only
Redis or Memcached stores. This is thanks to the speed of modern SSD drives,
which make the access-time penalty of using disk vs RAM insignificant for most
caching purposes. Simply put, you're now usually better off keeping a huge cache
on disk rather than a small cache in memory.