mirror of
https://github.com/netbirdio/FreeBSD-ports.git
synced 2026-05-22 18:42:42 -07:00
databases/rubygem-solid_queue-rails80: Add rubygem-solid_queue-rails80 1.2.4 (copied from rubygem-solid_queue-rails72)
This commit is contained in:
@@ -1072,6 +1072,7 @@
|
||||
SUBDIR += rubygem-solid_cache-rails80
|
||||
SUBDIR += rubygem-solid_queue
|
||||
SUBDIR += rubygem-solid_queue-rails72
|
||||
SUBDIR += rubygem-solid_queue-rails80
|
||||
SUBDIR += rubygem-sqlite3
|
||||
SUBDIR += rubygem-sqlite3-ruby
|
||||
SUBDIR += rubygem-sqlite31
|
||||
|
||||
@@ -0,0 +1,25 @@
|
||||
PORTNAME= solid_queue
|
||||
PORTVERSION= 1.2.4
|
||||
CATEGORIES= databases rubygems
|
||||
MASTER_SITES= RG
|
||||
PKGNAMESUFFIX= -rails80
|
||||
|
||||
MAINTAINER= sunpoet@FreeBSD.org
|
||||
COMMENT= Database-backed Active Job backend
|
||||
WWW= https://github.com/rails/solid_queue
|
||||
|
||||
LICENSE= MIT
|
||||
LICENSE_FILE= ${WRKSRC}/MIT-LICENSE
|
||||
|
||||
RUN_DEPENDS= rubygem-activejob80>=7.1:devel/rubygem-activejob80 \
|
||||
rubygem-activerecord80>=7.1:databases/rubygem-activerecord80 \
|
||||
rubygem-concurrent-ruby>=1.3.1:devel/rubygem-concurrent-ruby \
|
||||
rubygem-fugit>=1.11<2:devel/rubygem-fugit \
|
||||
rubygem-railties80>=7.1:www/rubygem-railties80 \
|
||||
rubygem-thor>=1.3.1:devel/rubygem-thor
|
||||
|
||||
USES= gem
|
||||
|
||||
NO_ARCH= yes
|
||||
|
||||
.include <bsd.port.mk>
|
||||
@@ -0,0 +1,3 @@
|
||||
TIMESTAMP = 1762586942
|
||||
SHA256 (rubygem/solid_queue-1.2.4.gem) = bb60f9552a969ac377d87601b0ff6a088f5e6f20b0cbbe3844a59d022cac0e4b
|
||||
SIZE (rubygem/solid_queue-1.2.4.gem) = 45056
|
||||
@@ -0,0 +1,13 @@
|
||||
Solid Queue is a DB-based queuing backend for Active Job, designed with
|
||||
simplicity and performance in mind.
|
||||
|
||||
Besides regular job enqueuing and processing, Solid Queue supports delayed jobs,
|
||||
concurrency controls, recurring jobs, pausing queues, numeric priorities per
|
||||
job, priorities by queue order, and bulk enqueuing (enqueue_all for Active Job's
|
||||
perform_all_later).
|
||||
|
||||
Solid Queue can be used with SQL databases such as MySQL, PostgreSQL or SQLite,
|
||||
and it leverages the FOR UPDATE SKIP LOCKED clause, if available, to avoid
|
||||
blocking and waiting on locks when polling jobs. It relies on Active Job for
|
||||
retries, discarding, error handling, serialization, or delays, and it's
|
||||
compatible with Ruby on Rails's multi-threading.
|
||||
Reference in New Issue
Block a user