NOTICE: This package has been removed from pkgsrc

./devel/ruby-activejob42, Job classes that can be run by a variety of queueing backends

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ]

Branch: CURRENT, Version: 4.2.11.1, Package name: ruby24-activejob42-4.2.11.1, Maintainer: minskim

Active Job is a framework for declaring jobs and making them run on a
variety of queueing 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, really.

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 of 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.


Required to run:
[devel/ruby-activesupport42] [devel/ruby-globalid] [lang/ruby24-base]

Required to build:
[pkgtools/cwrappers]

Master sites:

SHA1: 0f382c334aecddb61d7b710aa35d83a4c23c77df
RMD160: 920249d1aafdf410cf18a770a0eaa9c23b121a62
Filesize: 19 KB

Version history: (Expand)

CVS history: (Expand)


   2020-03-21 16:45:27 by Takahiro Kambe | Files touched by this commit (4) | Package removed
Log message:
devel/ruby-activejob42: remove package

Remove ruby-activejob42 package, a part of Ruby on Rails 4.2 package.
   2019-04-14 12:11:56 by Takahiro Kambe | Files touched by this commit (1) | Package updated
Log message:
devel/ruby-activejob42: update to 4.2.11.1

## Rails 4.2.11.1 (March 11, 2019) ##

*   No changes.
   2018-11-29 14:49:44 by Takahiro Kambe | Files touched by this commit (1) | Package updated
Log message:
devel/ruby-activejob42: update to 4.2.11

## Rails 4.2.11 (November 27, 2018) ##

*   Do not deserialize GlobalID objects that were not generated by Active Job.

    Trusting any GlobaID object when deserializing jobs can allow attackers to access
    information that should not be accessible to them.

    Fix CVE-2018-16476.

    *Rafael Mendonça França*
   2018-03-18 15:21:22 by Takahiro Kambe | Files touched by this commit (37) 
Log message:
lang/ruby: replace RUBY_RAILS_SUPPORTED to RUBY_RAILS_ACCEPTED

Change RUBY_RAILS_SUPPORTED to RUBY_RAILS_ACCEPTED for better wording.
   2018-03-13 17:30:15 by Takahiro Kambe | Files touched by this commit (1) | Package updated
Log message:
devel/ruby-activejob42: update to 4.2.10

No change except version.
   2017-06-21 15:12:21 by Takahiro Kambe | Files touched by this commit (19) | Package updated
Log message:
Switch most of Ruby on Rails related packages to updated frame work.
   2017-04-21 23:20:33 by Min Sik Kim | Files touched by this commit (4) 
Log message:
Import ruby-activejob-4.2.8 as devel/ruby-activejob42

Active Job is a framework for declaring jobs and making them run on a
variety of queueing 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, really.

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 of 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.