One gem per day for 20 days, in no particular order.
No explanations, no reviews, just README links. (16/20)
github.com/chaps-io/gush
One gem per day for 20 days, in no particular order.
No explanations, no reviews, just README links. (16/20)
github.com/chaps-io/gush
Add the `telesink-activejob` gem, set 1 env variable, and start tracking job execution events instantly.
Filter everything in the dashboard.
P.S. Looking for beta testers:
bsky.app/profile/kyry...
Add the `telesink-activejob` gem, set 1 env variable, and start tracking job execution events instantly.
Filter everything in the dashboard.
P.S. Looking for beta testers:
bsky.app/profile/kyry...
Telesink runs on Rails. For jobs: Solid Queue + Mission Control - great stack.
But one thing was missing: real-time visibility.
So I built it.
telesink.com/blog/telesin...
Telesink runs on Rails. For jobs: Solid Queue + Mission Control - great stack.
But one thing was missing: real-time visibility.
So I built it.
telesink.com/blog/telesin...
- their real app for managing client leads and the code within!
- balancing objects at the edge versus the center of your system
- how to remember iso8601, 11 years later 😂
- a bit of github.com/kaspth/activ... at the end
- their real app for managing client leads and the code within!
- balancing objects at the edge versus the center of your system
- how to remember iso8601, 11 years later 😂
- a bit of github.com/kaspth/activ... at the end
`perform_enqueued_jobs` creates odd situations when testing retries, because it performs the jobs immediately on the call to `enqueue`.
`flush_enqueued_jobs until enqueued_jobs.empty?` creates much more realistic scenarios, as it enqueues then performs.
`perform_enqueued_jobs` creates odd situations when testing retries, because it performs the jobs immediately on the call to `enqueue`.
`flush_enqueued_jobs until enqueued_jobs.empty?` creates much more realistic scenarios, as it enqueues then performs.
Enqueuing via ActiveJob::Base#perform_later triggers callbacks and generates one round-trip for each job. Bulk enqueuing skips callbacks and enqueues all jobs in one step.
Enqueuing via ActiveJob::Base#perform_later triggers callbacks and generates one round-trip for each job. Bulk enqueuing skips callbacks and enqueues all jobs in one step.
Get in bozo we're applying both ActiveRecord::AssociatedObject and ActiveJob::Performs to Action Mailbox!
buttondown.com/kaspth/archi...
Get in bozo we're applying both ActiveRecord::AssociatedObject and ActiveJob::Performs to Action Mailbox!
buttondown.com/kaspth/archi...
You can now see all the benefits and more praise quotes now that people are seeing this in practice — I'm really proud of where this is going! 🚀
You can now see all the benefits and more praise quotes now that people are seeing this in practice — I'm really proud of where this is going! 🚀
He’s building Lapsoss - a vendor-agnostic library for error tracking. Think ActiveJob, but for errors.
Switching from Sentry to Honeybadger? With Lapsoss, just change the adapter, the API stays the same.
He’s building Lapsoss - a vendor-agnostic library for error tracking. Think ActiveJob, but for errors.
Switching from Sentry to Honeybadger? With Lapsoss, just change the adapter, the API stays the same.
https://github.com/rails/rails/pull/55127
https://github.com/rails/rails/pull/55127
By: LordSarevok on Sunday, November 23, 2025
By: LordSarevok on Sunday, November 23, 2025
Google Slides:
docs.google.com/presentation...
GitHub Repo:
github.com/AndyObtiva/s...
#ruby #rails #rubyonrails #solidqueue #queuingbackend #messagequeues
Google Slides:
docs.google.com/presentation...
GitHub Repo:
github.com/AndyObtiva/s...
#ruby #rails #rubyonrails #solidqueue #queuingbackend #messagequeues
I think the front-end is an insanely complicated, creaky mess... with the exception of Turbo.
Oh and Rails CLI drives me crazy.
I think the front-end is an insanely complicated, creaky mess... with the exception of Turbo.
Oh and Rails CLI drives me crazy.
Real OG’s use ActiveJob for their sERvIcE oBjECt needs
RSpec is better
Heroku still champ
Real OG’s use ActiveJob for their sERvIcE oBjECt needs
RSpec is better
Heroku still champ