kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

devel/rubygem-sucker_punch: Add rubygem-sucker_punch 3.0.1

Browse source 
Sucker Punch is a single-process Ruby asynchronous processing library. This
reduces costs of hosting on a service like Heroku along with the memory
footprint of having to maintain additional jobs if hosting on a dedicated
server. All queues can run within a single application (eg. Rails, Sinatra,
etc.) process.

Sucker Punch is perfect for asynchronous processes like emailing, data
crunching, or social platform manipulation. No reason to hold up a user when you
can do these things in the background within the same process as your web
application.

Sucker Punch is built on top of concurrent-ruby. Each job is setup as a pool,
which equates to its own queue with individual workers working against the jobs.
Unlike most other background processing libraries, Sucker Punch's jobs are
stored in memory. The benefit to this is there is no additional infrastructure
requirement (ie. database, redis, etc.). However, if the web processes are
restarted with jobs remaining in the queue, they will be lost. For this reason,
Sucker Punch is generally recommended for jobs that are fast and non-mission
critical (ie. logs, emails, etc.).

WWW: https://github.com/brandonhilkert/sucker_punch
This commit is contained in:
Po-Chuan Hsieh 2022-01-12 00:42:52 +08:00
parent 5de66e47c3
commit c8047bc608
No known key found for this signature in database
GPG key ID: 9A4BD10F002DD04B
4 changed files with 46 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
devel/Makefile
View file

@ -6852,6 +6852,7 @@
SUBDIR += rubygem-structured_warnings
SUBDIR += rubygem-stud
SUBDIR += rubygem-subexec
SUBDIR += rubygem-sucker_punch
SUBDIR += rubygem-sugar-high
SUBDIR += rubygem-sumbur
SUBDIR += rubygem-sundawg_country_codes

21
devel/rubygem-sucker_punch/Makefile Normal file
View file

@ -0,0 +1,21 @@
# Created by: Po-Chuan Hsieh <sunpoet@FreeBSD.org>
PORTNAME= sucker_punch
PORTVERSION= 3.0.1
CATEGORIES= devel rubygems
MASTER_SITES= RG
MAINTAINER= sunpoet@FreeBSD.org
COMMENT= Asynchronous processing library for Ruby
LICENSE= MIT
LICENSE_FILE= ${WRKSRC}/LICENSE.txt
RUN_DEPENDS= rubygem-concurrent-ruby>=1.0<2:devel/rubygem-concurrent-ruby
USES= gem
USE_RUBY= yes
NO_ARCH= yes
.include <bsd.port.mk>

3
devel/rubygem-sucker_punch/distinfo Normal file
View file

@ -0,0 +1,3 @@
TIMESTAMP = 1641045730
SHA256 (rubygem/sucker_punch-3.0.1.gem) = b49319778750e56b8c5add6a227727ef3dc3c327756bdf7e3bf236cb89d05579
SIZE (rubygem/sucker_punch-3.0.1.gem) = 18432

21
devel/rubygem-sucker_punch/pkg-descr Normal file
View file

@ -0,0 +1,21 @@
Sucker Punch is a single-process Ruby asynchronous processing library. This
reduces costs of hosting on a service like Heroku along with the memory
footprint of having to maintain additional jobs if hosting on a dedicated
server. All queues can run within a single application (eg. Rails, Sinatra,
etc.) process.
Sucker Punch is perfect for asynchronous processes like emailing, data
crunching, or social platform manipulation. No reason to hold up a user when you
can do these things in the background within the same process as your web
application.
Sucker Punch is built on top of concurrent-ruby. Each job is setup as a pool,
which equates to its own queue with individual workers working against the jobs.
Unlike most other background processing libraries, Sucker Punch's jobs are
stored in memory. The benefit to this is there is no additional infrastructure
requirement (ie. database, redis, etc.). However, if the web processes are
restarted with jobs remaining in the queue, they will be lost. For this reason,
Sucker Punch is generally recommended for jobs that are fast and non-mission
critical (ie. logs, emails, etc.).
WWW: https://github.com/brandonhilkert/sucker_punch