mastodon.ie is one of the many independent Mastodon servers you can use to participate in the fediverse.
Irish Mastodon - run from Ireland, we welcome all who respect the community rules and members.

Administered by:

Server stats:

1.6K
active users

#solidqueue

0 posts0 participants0 posts today
Ruby Central<p>We'll also have the one-and-only Rosa Gutierrez, Maintainer of <a href="https://ruby.social/tags/SolidQueue" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SolidQueue</span></a>!</p>
alexanderadam<p>It's always great to see <span class="h-card" translate="no"><a href="https://tu.social/@rosa" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>rosa</span></a></span> and she talked about her <a href="https://ruby.social/tags/SolidQueue" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SolidQueue</span></a> implementation at <a href="https://ruby.social/tags/rubycommunityconference" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rubycommunityconference</span></a> in <a href="https://ruby.social/tags/krakow" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>krakow</span></a>.</p><p>She also gave a shout-out to <span class="h-card" translate="no"><a href="https://ruby.social/@bensheldon" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>bensheldon</span></a></span>'s <a href="https://ruby.social/tags/goodjob" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>goodjob</span></a> and mentioned how <span class="h-card" translate="no"><a href="https://ruby.social/@getajobmike" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>getajobmike</span></a></span>'s <span class="h-card" translate="no"><a href="https://ruby.social/@sidekiq" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>sidekiq</span></a></span> is blazingly fast.</p><p><a href="https://ruby.social/tags/ruby" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ruby</span></a> <a href="https://ruby.social/tags/rails" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rails</span></a> <a href="https://ruby.social/tags/queue" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>queue</span></a> <a href="https://ruby.social/tags/rubyonrails" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rubyonrails</span></a> <a href="https://ruby.social/tags/activerecord" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>activerecord</span></a> <a href="https://ruby.social/tags/poland" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>poland</span></a> <a href="https://ruby.social/tags/37signals" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>37signals</span></a> <a href="https://ruby.social/tags/backgroundprocessing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>backgroundprocessing</span></a> <a href="https://ruby.social/tags/backgroundprocesses" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>backgroundprocesses</span></a> <a href="https://ruby.social/tags/sidekiq" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sidekiq</span></a></p>
Jan Peterka<p>I'm adding background jobs to my new app (Rails7.2 + SolidQueue), and not sure how things should be designed.<br>I need to run daily job to generate notifications on user-created task due/reminder date.</p><p>Should I:</p><p>1) create one job that iterates all relevant tasks and generates notifications? (might get slow with more users)</p><p>2) have one job that iterates tasks, and creates separate job for every relevant task?</p><p>3) something else?</p><p><a href="https://ruby.social/tags/rubyonrails" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rubyonrails</span></a> <a href="https://ruby.social/tags/activejob" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>activejob</span></a> <a href="https://ruby.social/tags/SolidQueue" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SolidQueue</span></a></p>
Honeybadger.io<p>Picture this: you're six months into a fresh Rails app that processes business-critical jobs with Solid Queue—and you deployed a bug that is wreaking havoc in thousands of jobs. How do you find them?</p><p>You'll wish you'd read our latest article from Jeffery Morhous!</p><p><a href="https://www.honeybadger.io/blog/solid-queue-lifecycle/?utm_source=mastodon&amp;utm_medium=social" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">honeybadger.io/blog/solid-queu</span><span class="invisible">e-lifecycle/?utm_source=mastodon&amp;utm_medium=social</span></a></p><p><a href="https://honeybadger.social/tags/Ruby" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ruby</span></a> <a href="https://honeybadger.social/tags/RubyOnRails" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RubyOnRails</span></a> <a href="https://honeybadger.social/tags/SolidQueue" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SolidQueue</span></a> <a href="https://honeybadger.social/tags/ActiveJob" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ActiveJob</span></a> <a href="https://honeybadger.social/tags/SQlite" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SQlite</span></a></p>