Up to [cvs.NetBSD.org] / pkgsrc / devel / ruby-activejob42
Request diff between arbitrary revisions
Default branch: MAIN
Current tag: MAIN
Revision 1.4, Sat Mar 21 15:45:26 2020 UTC (4 years ago) by taca
Branch: MAIN
CVS Tags: HEAD
Changes since 1.3: +1 -1
lines
FILE REMOVED
devel/ruby-activejob42: remove package Remove ruby-activejob42 package, a part of Ruby on Rails 4.2 package.
Revision 1.3 / (download) - annotate - [select for diffs], Sun Mar 18 14:21:20 2018 UTC (6 years, 1 month ago) by taca
Branch: MAIN
CVS Tags: pkgsrc-2019Q4-base,
pkgsrc-2019Q4,
pkgsrc-2019Q3-base,
pkgsrc-2019Q3,
pkgsrc-2019Q2-base,
pkgsrc-2019Q2,
pkgsrc-2019Q1-base,
pkgsrc-2019Q1,
pkgsrc-2018Q4-base,
pkgsrc-2018Q4,
pkgsrc-2018Q3-base,
pkgsrc-2018Q3,
pkgsrc-2018Q2-base,
pkgsrc-2018Q2,
pkgsrc-2018Q1-base,
pkgsrc-2018Q1
Changes since 1.2: +2 -2
lines
Diff to previous 1.2 (colored)
lang/ruby: replace RUBY_RAILS_SUPPORTED to RUBY_RAILS_ACCEPTED Change RUBY_RAILS_SUPPORTED to RUBY_RAILS_ACCEPTED for better wording.
Revision 1.2 / (download) - annotate - [select for diffs], Wed Jun 21 13:12:20 2017 UTC (6 years, 9 months ago) by taca
Branch: MAIN
CVS Tags: pkgsrc-2017Q4-base,
pkgsrc-2017Q4,
pkgsrc-2017Q3-base,
pkgsrc-2017Q3,
pkgsrc-2017Q2-base,
pkgsrc-2017Q2
Changes since 1.1: +3 -2
lines
Diff to previous 1.1 (colored)
Switch most of Ruby on Rails related packages to updated frame work.
Revision 1.1 / (download) - annotate - [select for diffs], Fri Apr 21 21:20:33 2017 UTC (6 years, 11 months ago) by minskim
Branch: MAIN
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.