Resque Reviews

Gitea Reviews

Resque mentions (7)

• It’s Time For Active Job

  It is hard to imagine any big and complex Rails project without background jobs processing. There are many gems for this task: **Delayed Job, Sidekiq, Resque, SuckerPunch** and more. And Active Job has arrived here to rule them all. - Source: dev.to / 24 days ago

• How to Setup a Project That Can Host Up to 1000 Users for Free

  Rollbar is a great error-tracking service. It alerts us on exceptions and errors, provides analysis tools and dashboard, so we can see, reproduce, and fix bugs quickly when something went wrong. This service has a possibility to log not only uncaught exceptions but any messages. By default, the messages are reported synchronously, but you can enable asynchronous reporting using Sidekiq, girl_friday, or Resque.... - Source: dev.to / 27 days ago

• Add web scraping data into the database at regular intervals [ruby & ror]

  You can use a background job queue like Resque to scrape and process data in the background, and a scheduler like resque-scheduler to schedule jobs to run your scraper periodically. Source: about 2 years ago

• How to run a really long task from a Rails web request

  So how do we trigger such a long-running process from a Rails request? The first option that comes to mind is a background job run by some of the queuing back-ends such as Sidekiq, Resque or DelayedJob, possibly governed by ActiveJob. While this would surely work, the problem with all these solutions is that they usually have a limited number of workers available on the server and we didn’t want to potentially... - Source: dev.to / about 2 years ago

• Building a dynamic staging platform

  Background jobs are another limitation. Since only the Aha! Web service runs in a dynamic staging, the host environment's workers would process any Resque jobs that were sent to the shared Redis instance. If your branch hadn't updated any background-able methods, this would be no big deal. But if you were hoping to test changes to these methods, you would be out of luck. - Source: dev.to / about 2 years ago

Gitea mentions (60)

• Beware Offers of “Help” with Your Projects

  This reminds me of Gogs [0], where the original author refused a lot of good ideas and improvements, eventually leading to a fork [1] that's now a lot more popular and active than the original. [0] https://gogs.io/ [1] https://gitea.io/en-us/. - Source: Hacker News / about 1 year ago

• Incident with Issues and Pull Requests

  Yes, we do this using https://gitea.io/en-us/ on a private server. Firewall, backups and a replica running for most projects. Github is only used when it's required by a stakeholder. - Source: Hacker News / about 1 year ago

• Let's Make Sure GitHub Doesn't Become the Only Option

  There's a number of places out there, some of which also support alternatives to Git itself. By no means a complete list and in no particular order: GitLab - https://about.gitlab.com/ Sourcehut - https://sourcehut.org/ Codeberg - https://codeberg.org/ Launchpad - https://launchpad.net/ Debian Salsa - https://salsa.debian.org/public Pagure - https://pagure.io/pagure For self hsoted options, there's these below... - Source: Hacker News / about 1 year ago

• If you're on DSM 6 and still waiting for an update on the GitLab package, don't bother

  And if you need GitLab (for runner, etc...) then it's not too bad to run in Docker. But if anyone is looking for a somewhat simpler git solution, gitea is pretty great. Source: about 1 year ago

• OpenBSD Upgrade 7.2 to 7.3

  Check: Configuration and syntax changes and Special packages. The latter includes changes on PostgreSQL, Python and Gitea. - Source: dev.to / about 1 year ago