A JavaScript module that defines a PeriodicTask constructor, easing the way you use setTimeout to run periodic tasks.
android foreground service with turbo module with periodic task and notification
Given a point and a distance, determine how many periodic values were skipped.
Find the nearest value of a discrete periodic function, given a point.
Find how many values of a discrete periodic function are contained in an interval.
micromark extension to support GFM task list items
mdast extension to parse and serialize GFM task list items
Amazon Connect Streams Library
A shim for the setImmediate efficient script yielding API
A simple tool to keep requests to be executed in order.
High-priority task queue for Node.js and browsers
task item extension for tiptap
task list extension for tiptap
High-priority task queue for Node.js and browsers
Fastify plugin for scheduling periodic jobs
MediaPipe Vision Tasks
Periodic background tasks for React Native apps, cross-platform (iOS and Android), which run even when the app is closed.
A fast, efficient Node.js Worker Thread Pool implementation
A markdown-it plugin to create GitHub-style task lists
No description provided.
List of ML tasks for huggingface.co/tasks
💯 PEM-to-JWK and JWK-to-PEM for RSA keys in a lightweight, zero-dependency library focused on perfect universal compatibility.
Task and Message Queues with Multiple Providers
TypeScript definitions for undertaker-registry
Controls execution of periodic scheduled tasks.
Periodically run tasks that fetch data
a Rails 2.3, Rails 3, and Ruby compatible scheduler daemon. Replaces cron/rake pattern of periodically running rake tasks to perform maintenance tasks, only loading the environment ONCE.
a Rails 2.3, Rails 3, and Ruby compatible scheduler daemon. Replaces cron/rake pattern of periodically running rake tasks to perform maintenance tasks, only loading the environment ONCE.
a Rails 2.3, Rails 3, and Ruby compatible scheduler daemon. Replaces cron/rake pattern of periodically running rake tasks to perform maintenance tasks, only loading the environment ONCE.
Define your maintenance checks, e.g. disk usage, mysql status, etc. Then run these checks on multiple servers using rake, and have the results emailed back to you. Set up a cron job to run the rake task on a regular period, and BANG! You've got simple and effective server monitoring.
Use two scripts, itgwiki_mirror_backup and itgwiki_mirror_deploy, to maintain a read-only mirror of ITGwiki. itgwiki_mirror_backup runs periodically and automatically on the live instance of ITGwiki to create a backup and copy it to the mirror. itgwiki_mirror_deploy runs on the mirror and is triggered by itgwiki_mirror_backup, imports and adjusts the backup to be read-only, then deploys it on the mirror server. Requires rsync and mysqldump. IMPORTANT: database user passwords are visible as part of the command used to execute the backup and deploy processes. I recommend creating minimally empowered user accounts to execute backup and deploy tasks.
Track counts and compute rate of iteration. Set up callbacks for various intervals such as every n increments or every n ticks. computer = Cadence::Computer.new do |c| c.every 5 do p [:completed_processing, n] end end computer.start do |c| 1.upto(100) do |n| c.next # do magic here end end Mostly intended for providing intermitent feedback of the progress of tasks that will run for lengthy periods of time. Rudimentary support for time-based callbacks is possible through #ticks.
Mount SolidQueueWeb in any Rails app using Solid Queue to get a full-featured job dashboard: inspect jobs by status (ready, scheduled, running, blocked, failed), retry or discard failed jobs, reschedule or run scheduled jobs immediately, manage recurring tasks, filter by queue/priority/period, export to CSV, detect slow jobs, view queue depth sparklines, track job performance (p50/p95), and scrape a /metrics JSON endpoint for external monitoring — all without leaving your app.
There are many software applications that aim to watch processes, and keep them alive and clean. Some of them are well known: god, monit, bluepill. All have good and bad sides. One of the bad sides is that each alternative is based on a deamon that computes data and then sleeps for a while. Who is monitoring this particular deamon ? What if this process suddenly stops ? Also, you often need root rights to run those tools. On some hosting environments (mainly in shared hosting), this is an issue. Ziltoid is an attempt to solve those issues using the crontab system, which comes with many good sides : it's on every system, it launches a task periodically then waits for an amount of time, it doesn't need monitoring, it can send emails to warn of an error and it can run any script.
# Squash Migrations Periodically squash migrations to reduce overhead of the `db:migrate` Rake task. ## Creating a release 1. Create a new pull request that: - Bumps the version in `rails-squash-migrations.gemspec` - Updates `CHANGELOG.md` to include all noteworthy changes, the release version, and the release date. 2. After the pull request lands, checkout the most up to date `main` branch and build the gem: ```console $ docker run --rm -it -v $(pwd):$(pwd) -w $(pwd) ruby gem build ``` 3. Publish the gem: ```console $ docker run --rm -it -v $(pwd):$(pwd) -w $(pwd) ruby gem push rails-squash-migrations-X.Y.Z.gem ``` 4. Create and publish a git tag: ```console $ git tag X.Y.Z $ git push https://github.com/Pioneer-Valley-Books/rails-squash-migrations.git X.Y.Z ```
http://www.engineyard.com/blog/2010/extending-rails-3-with-railties/ http://www.igvita.com/2010/08/04/rails-3-internals-railtie-creating-plugins/ h1. Morning Glory Morning Glory is comprised of a rake task and helper methods that manages the deployment of static assets into an Amazon CloudFront CDN's S3 Bucket, improving the performance of static assets on your Rails web applications. _NOTE: You will require an Amazon Web Services (AWS) account in order to use this gem. Specially: S3 for storing the files you wish to distribute, and CloudFront for CDN distribution of those files._ This version of Morning Glory works with Rails 3.x and Ruby 1.9.x h2. What does it do? Morning Glory provides an easy way to deploy Ruby on Rails application assets to the Amazon CloudFront CDN. It solves a number of common issues with S3/CloudFront. For instance, CloudFront won't automatically expire old assets stored on edge nodes when you redeploy new assets (the Cloudfront expiry time is 24 hours minimum). To fix this Morning Glory will automatically namespace asset releases for you, then update all references to those renamed assets within your stylesheets ensuring there are no broken asset links. It also provides a helper method to rewrite all standard Rails asset helper generated URLs to your CloudFront CDN distributions, as well as handling switching between HTTP and HTTPS. Morning Glory was also built with SASS (Syntactically Awesome Stylesheets) in mind. If you use Sass for your stylesheets they will automatically be built before deployment to the CDN. See http://sass-lang.com/ for more information on Sass.s h2. What it doesn't do Morning Glory cannot configure your CloudFront distributions for you automatically. You will manually have to login to your AWS Management Console account, "https://console.aws.amazon.com/cloudfront/home":https://console.aws.amazon.com/cloudfront/home, and set up a distribution pointing to an S3 Bucket. h2. Installation <pre> gem 'morning_glory' </pre> h2. Usage Morning Glory provides it's functionality via rake tasks. You'll need to specify the target rails environment configuration you want to deploy for by using the @RAILS_ENV={env}@ parameter (for example, @RAILS_ENV=production@). <pre> rake morning_glory:cloudfront:deploy RAILS_ENV={YOUR_TARGET_ENVIRONMENT} </pre> h2. Configuration h3. The Morning Glory configuration file, @config/morning_glory.yml@ You can specify a configuration section for every rails environment (production, staging, testing, development). This section can have the following properties defined: <pre> --- production: enabled: true # Is MorningGlory enabled for this environment? bucket: cdn.production.foo.com # The bucket to deploy your assets into s3_logging_enabled: true # Log the deployment to S3 revision: "20100317134627" # The revision prefix. This timestamp automatically generateed on deployment delete_prev_rev: true # Delete the previous asset release (save on S3 storage space) </pre> h3. The Amazon S3 authentication keys configuration file, @config/s3.yml@ This file provides the access credentials for your Amazon AWS S3 account. You can configure keys for all your environments (production, staging, testing, development). <pre> --- production: access_key_id: YOUR_ACCESS_KEY secret_access_key: YOUR_SECRET_ACCESS_KEY </pre> Note: If you are deploying your system to Heroku, you can configure your Amazon AWS S3 information with the environment variables S3_KEY and S3_SECRET instead of using a configuration file. h3. Set up an asset_host For each environment that you'd like to utilise the CloudFront CDN for you'll need to define the asset_host within the @config/environments/{ENVIRONMENT}.rb@ configuration file. As of June 2010 AWS supports HTTPS requests on the CloudFront CDN, so you no longer have to worry about switching servers. (Yay!) h4. Example config/environments/production.rb @asset_host@ snippet: Here we're targeting a CNAME domain with HTTP support. <pre> ActionController::Base.asset_host = Proc.new { |source, request| if request.ssl? "#{request.protocol}#{request.host_with_port}" else "#{request.protocol}assets.example.com" end } </pre> h3. Why do we have to use a revision-number/namespace/timestamp? Once an asset has been deployed to the Amazon Cloudfront edge servers it cannot be modified - the version exists until it expires (minimum of 24 hours). To get around this we need to prefix the asset path with a revision of some sort - in MorningGlory's case we use a timestamp. That way you can deploy many times during a 24 hour period and always have your latest revision available on your web site. h2. Dependencies h3. AWS S3 Required for uploading the assets to the Amazon Web Services S3 buckets. See "http://amazon.rubyforge.org/":http://amazon.rubyforge.org/ for more documentation on installation. h2. About the name Perhaps not what you'd expect; a "Morning Glory":http://en.wikipedia.org/wiki/Morning_Glory_cloud is a rare cloud formation observed by glider pilots in Australia (see my side project, "YourFlightLog.com for flight-logging software for paraglider and hang-glider pilots":http://www.yourflightlog.com, from which the Morning Glory plugin was originally extracted). Copyright (c) 2010 "@AdamBurmister":http://twitter.com/adamburmister/, released under the MIT license
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.