notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
Want a good monitor light? See my photosAll times are UTC
Ukraine
Port details
rubygem-activejob72 Declare job classes that can be run by a variety of queuing backends
7.2.1 develnew! on this many watch lists=0 search for ports that depend on this port Find issues related to this port Report an issue related to this port View this port on Repology. pkg-fallout 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 search for ports maintained by this maintainer
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.
HomepageHomepage    cgit ¦ Codeberg ¦ GitHub ¦ GitLab ¦ SVNWeb - no subversion history for this port

Manual pages:
FreshPorts has no man page information for this port.
pkg-plist: as obtained via: make generate-plist
Expand this list (3 items)
Collapse this list.
  1. /usr/local/share/licenses/rubygem-activejob72-7.2.1/catalog.mk
  2. /usr/local/share/licenses/rubygem-activejob72-7.2.1/LICENSE
  3. /usr/local/share/licenses/rubygem-activejob72-7.2.1/MIT
Collapse this list.
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:
  1. ruby32 : lang/ruby32
  2. gem : devel/ruby-gems
Runtime dependencies:
  1. rubygem-activesupport72>=7.2.1<7.2.1_99 : devel/rubygem-activesupport72
  2. rubygem-globalid-rails72>=0.3.6 : databases/rubygem-globalid-rails72
  3. ruby32 : lang/ruby32
  4. gem : devel/ruby-gems
Patch dependencies:
  1. ruby32 : lang/ruby32
  2. gem : devel/ruby-gems
Extract dependencies:
  1. ruby32 : lang/ruby32
This port is required by:
for Run
  1. databases/rubygem-solid_cable
  2. databases/rubygem-solid_cache
  3. databases/rubygem-solid_queue
  4. mail/rubygem-actionmailbox72
  5. mail/rubygem-actionmailer72
  6. net/rubygem-activestorage72
  7. www/rubygem-rails72
Expand this list (8 items / 1 hidden - sorry, this count includes any deleted ports)
  1. Collapse this list).
  2. www/rubygem-turbo-rails
  3. Collapse this list.

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:
Expand this list (1 items)
Collapse this list.
  1. https://rubygems.org/downloads/
Collapse this list.

Number of commits found: 1

Commit History - (may be incomplete: for full details, see links to repositories near top of page)
CommitCreditsLog message
7.2.1
18 Sep 2024 06:13:01
commit hash: a180c280168a6f57629d84368487d0c0cdb38b4ccommit hash: a180c280168a6f57629d84368487d0c0cdb38b4ccommit hash: a180c280168a6f57629d84368487d0c0cdb38b4ccommit hash: a180c280168a6f57629d84368487d0c0cdb38b4c files touched by this commit
Po-Chuan Hsieh (sunpoet) search for other commits by this committer
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