Results for any-touch

Emerald is a generator for RDoc, like standard Darkfish, but looks much better (and does not have this touch of green). It is inspired by Hanna, but does not share any code with it (and does not use frames!).

Provides methods to publish and unpublish your active record models based on a boolean flag, a date, or a datetime. Also adds named scopes to nicely filter your records. Does not touch any controller or views.

Colorize terminal output without touching core classes. Work for Linux and Mac, require `win32console` for Windows. Use on any class, auto #puts or #print, with power of ruby blocks.

Use a convenient and expressive DSL to feed the Status Board App by Panic with custom data. Benefit directly from rubys expressiveness without having to touch any server-related code.

Thermos is a Rails caching library that keeps your cache always warm by automatically rebuilding it in the background when ActiveRecord models change. No more stale data from TTL expiration, no more slow cold cache hits, and no need to 'touch' associated models. Works with any ActiveJob backend (Sidekiq, Solid Queue, etc.) and any cache store (Redis, Memcached, Solid Cache, etc.). Perfect for API responses, JSON serialization, and view caching.

https://rubygems.org/gems/apoptosis I got the idea for this gem during JRubyConf during Michael Feathers' talk. He made a point that software is alive and unlike biological systems, doesn't have an automatic way to kill off old 'cells'. This gem is to aid in finding old, potentially crufty areas of your project that may need to be killed off and remade, or at least looked at. Currently the gem alerts you to any lines that haven't been touched in at least a year. \ gem install apoptosis Navigate to a project directory which is also a git repository and run the command: apoptosis This command will create a DeathRow.md file in the directory with a list of files and lines in your project which have not been touched in a year. The idea is that you should re-evaluate and/or refactor them.

For SaaS applications, there are times when we dont want to show the resource id to the user since its being shared with multiple companies that have signed up. And for scenarios where we want the URL to show numbers and not worded URL's like what friendly_id provide, this is the gem for you! It'll create id's sequentially starting from 1 for each relation parent/nested resource relation definedi\n Feel free to get in touch for any specific questions until the help, support group and readme are not done at info@7vals.com \n http://www.7vals.com

if/case conditionals can get really hairy in highly sophisticated business domains. Domain model inheritance can help remedy the problem, but you don't want to dump all logic variations in the same domain models. Strategy Pattern solves that problem by externalizing logic variations to separate classes outside the domain models. One difficulty with implementing Strategy Pattern is making domain models aware of newly added strategies without touching their code (Open/Closed Principle). Strategic solves that problem by supporting Strategy Pattern with automatic discovery of strategies and ability fetch the right strategy without conditionals. This allows you to make any domain model "strategic" by simply following a convention in the directory/namespace structure you create your strategies under so that the domain model automatically discovers all available strategies.

Drop-in honeypot spam protection for any Rack-based app. Combines an invisible form field, a submission-timing check, and a JavaScript input signals tracker (mouse, touch, scroll, keyboard, focus) into a single framework-agnostic gem, with an opt-in Hanami adapter. Ruby companion to the Crystal lucky_honeypot shard.

What is send? ============= It’s a tiny wee ruby gem that is a fork of [Object#try](http://ozmm.org/posts/try.html) and [Object#try from Rails](http://api.rubyonrails.org/classes/Object.html#M000027). It will *never* throw a NoMethodError (no matter the receiver), and returns nil if called on a nil-class or if the method in the receiver does not exist. Note on Patches/Pull Requests ----------------------------- 1. [Fork me!](http://github.com/Burgestrand/send-/fork) 2. Write tests for your new feature or bug fix (important, I don’t want to break your stuff in a future update by accident!) 3. Hack away on the code; make your tests pass. 4. Commit! Don’t touch Rakefile, version or git history in any of the commits you want me to pick. 5. ??? 6. Send me a pull request!

Online logging solution (like [Datadog](https://www.datadoghq.com)) have drastically transform the way we log. An app will nowdays logs dozen (hundred) of logs per requests. The issue is often to correlate this logs, with the initiating request (or job) and add shared metadata on this logs. Here come `ContextualizedLogs`. The main idea is to enhance your logs from your controller (including `ContextualizedController`, which use a before action), which will add the params to your logs (and some metadata about the request itself, like `request.uuid`). This metadata are stored in a `ActiveSupport::CurrentAttributes` which is a singleton (reset per request). Each subsequent logs in this thread (request) will also be enriched with this metadata, making it easier to find all the logs associated with a request (`uuid`, `ip`, `params.xxx`). On top of this, logs can also be enriched by the ActiveRecord model they use (`create` or `find`) (models including `ContextualizedModel`). So any time a contextualized model is created or find, some metadata related to the model (`id`, ...) will also be added to the logs. Allowing you to find all logs which "touched" this models.

aias turns AIA prompt files into unattended cron jobs. Add a schedule: key to any prompt's YAML frontmatter and run `aias update` to install the full set, or `aias add <path>` to install a single prompt without touching the rest. Schedules accept raw cron expressions or natural-language strings ("every weekday at 9am"). Run `aias install` once to capture your PATH, API keys, and AIA variables into env.sh — every job sources it at runtime. Output is written to a per-prompt log under ~/.config/aia/schedule/logs/. Prompts are self-describing — no separate configuration file is needed.

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.