I would look into setting up a Cron job to do that automatically, it's not really programming related but essentially you would do so using cPanel or whatever your web host uses. You can look into easycron.com for a better idea of how it works. Source: over 1 year ago

I use Easycron it has a free tier and the paid plan starts at $12/yr. Source: almost 2 years ago

Now to update this every once in a while. Basically, what I did was just hook the hotlist algorithm up to an api route and stick it into https://easycron.com. - Source: dev.to / over 2 years ago

Try webcron service easycron.com out, I think it allows unlimited cron tasks. Source: about 3 years ago

Echoing using easycron.com in vercel's integration. Super easy to use. Source: about 3 years ago

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 / about 11 hours ago

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: almost 2 years ago

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

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

The Schedules worker corresponds to the appwrite-schedule service in the docker-compose file. The Schedules worker uses a Resque Scheduler under the hood and handles the scheduling of CRON jobs across Appwrite. This includes CRON jobs from the Tasks API, Webhooks API, and the functions API. - Source: dev.to / about 3 years ago