Port details |
- rubygem-activejob72 Declare job classes that can be run by a variety of queuing backends
- 7.2.1 devel
=0 Package not present on quarterly.This port was created during this quarter. It will be in the next quarterly branch but not the current one.
- Maintainer: sunpoet@FreeBSD.org
- Port Added: 2024-09-18 06:21:29
- Last Update: 2024-09-18 06:13:01
- Commit Hash: a180c28
- Also Listed In: rubygems
- License: MIT
- WWW:
- https://github.com/rails/rails/tree/main/activejob
- https://rubyonrails.org/
- Description:
- Active Job is a framework for declaring jobs and making them run on a variety of
queuing backends. These jobs can be everything from regularly scheduled
clean-ups, to billing charges, to mailings -- anything that can be chopped up
into small units of work and run in parallel.
It also serves as the backend for Action Mailer's #deliver_later functionality
that makes it easy to turn any mailing into a job for running later. That's one
of the most common jobs in a modern web application: sending emails outside the
request-response cycle, so the user doesn't have to wait on it.
The main point is to ensure that all Rails apps will have a job infrastructure
in place, even if it's in the form of an "immediate runner". We can then have
framework features and other gems build on top of that, without having to worry
about API differences between Delayed Job and Resque. Picking your queuing
backend becomes more of an operational concern, then. And you'll be able to
switch between them without having to rewrite your jobs.
- ¦ ¦ ¦ ¦
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - Dependency lines:
-
- rubygem-activejob72>0:devel/rubygem-activejob72
- To install the port:
- cd /usr/ports/devel/rubygem-activejob72/ && make install clean
- To add the package, run one of these commands:
- pkg install devel/rubygem-activejob72
- pkg install rubygem-activejob72
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.- PKGNAME: rubygem-activejob72
- Flavors: there is no flavor information for this port.
- distinfo:
- TIMESTAMP = 1726487286
SHA256 (rubygem/activejob-7.2.1.gem) = eb145f5aaf8276f37b9e4e9f72f3d56b1733172b4be680e836c765f2e6a3c503
SIZE (rubygem/activejob-7.2.1.gem) = 36352
No package information for this port in our database- Sometimes this happens. Not all ports have packages. This is doubly so for new ports, like this one.
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- ruby32 : lang/ruby32
- gem : devel/ruby-gems
- Runtime dependencies:
-
- rubygem-activesupport72>=7.2.1<7.2.1_99 : devel/rubygem-activesupport72
- rubygem-globalid-rails72>=0.3.6 : databases/rubygem-globalid-rails72
- ruby32 : lang/ruby32
- gem : devel/ruby-gems
- Patch dependencies:
-
- ruby32 : lang/ruby32
- gem : devel/ruby-gems
-
- This port is required by:
- for Run
-
- databases/rubygem-solid_cable
- databases/rubygem-solid_cache
- databases/rubygem-solid_queue
- mail/rubygem-actionmailbox72
- mail/rubygem-actionmailer72
- net/rubygem-activestorage72
- www/rubygem-rails72
Configuration Options:
- No options to configure
- Options name:
- devel_rubygem-activejob72
- USES:
- cpe gem
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
Number of commits found: 1
Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
Commit | Credits | Log message |
7.2.1 18 Sep 2024 06:13:01 |
Po-Chuan Hsieh (sunpoet) |
devel/rubygem-activejob72: Add rubygem-activejob72 7.2.1
Active Job is a framework for declaring jobs and making them run on a variety of
queuing backends. These jobs can be everything from regularly scheduled
clean-ups, to billing charges, to mailings -- anything that can be chopped up
into small units of work and run in parallel.
It also serves as the backend for Action Mailer's #deliver_later functionality
that makes it easy to turn any mailing into a job for running later. That's one
of the most common jobs in a modern web application: sending emails outside the
request-response cycle, so the user doesn't have to wait on it.
The main point is to ensure that all Rails apps will have a job infrastructure
in place, even if it's in the form of an "immediate runner". We can then have
framework features and other gems build on top of that, without having to worry
about API differences between Delayed Job and Resque. Picking your queuing
backend becomes more of an operational concern, then. And you'll be able to
switch between them without having to rewrite your jobs. |
Number of commits found: 1
|