Search Results for "rules"

...To install for older versions, update Bundler at least 1.12: gem update bundler and Bundler should correctly resolve to earlier gems for your given Ruby version. Guard automates various tasks by running custom rules whenever file or directories are modified. It's frequently used by software developers, web designers, writers and other specialists to avoid mundane, repetitive actions and commands such as "relaunching" tools after changing source files or configurations. Common use cases include: an IDE replacement, web development tools, designing "smart" and "responsive" build systems/workflows, automating various project tasks and installing/monitoring various system services.

Grape is a Ruby framework for building REST-like APIs with a focus on simplicity and convention. It provides a DSL for declaring endpoints, parameters, formats, and validation rules, making it easy to build consistent and documented APIs. Grape supports multiple content types (JSON, XML, etc.), versioning, error handling, and authentication hooks, which are crucial for maintaining long-lived APIs. It integrates well with frameworks like Rails or Sinatra but can also be used standalone for microservices. Built-in tools like parameter coercion, strong validations, and automatic documentation (via Swagger integrations) reduce boilerplate and improve maintainability. ...

...Each policy method returns a boolean, and can be structured using combinators or shared logic to keep things DRY. In controllers and views, Pundit provides helpers like authorize, policy_scope, and policy to enforce those rules cleanly and consistently. The policy_scope feature is especially helpful—it restricts index or list queries to only the records the current user can see by applying scopes defined in the policy class. Pundit encourages placing authorization logic close to the model domain without muddling controllers or views, making permissions easier to reason about and testable.

...People also agree it's easier to work in codebases that exhibit a consistent style and format. So, what's the problem? No two developers will ever agree on what all the rules and format should be.

Software build environment based on Jam (http://www.perforce.com/jam/jam.html). Provided project description rules shift emphasis from how to build the software to what the software to build with central configuration of concrete build actions. Moved to: https://github.com/tsc-collection/tsc-build Now part of GitHub's TSC Collection available at https://github.com/tsc-collection

Beta state! tisift: scaning folder and sort messages with given filter rules. tish: imap shell = imap command line tools. Example: # Set MsgId on Mails without one FOLDER="Archives" ; tils -I "$FOLDER" |grep "\{"|while read LINE ; do tish -x addheader "$FOLDER" "$LINE" "X-New-Header: true" ; done # Correct Date to second received header: tish date Archives PATTERN received2 # Import or export mbox tish exportmbox Archives >file.mbox tish importmbox Archives <file.mbox Written in ruby. ...

...It centralizes all authorization logic in a single Ability class, where you define what actions each type of user can or cannot perform on different resources. Developers then use helpers like authorize! in controllers or can? in views to enforce those rules without scattering permission logic across the application. It supports defining permissions using conditions, allowing granular access based on attributes like ownership or role. Because it abstracts authorization cleanly, applications stay easier to read, test, and maintain as business rules evolve. Though no longer actively maintained in its original form, CanCan inspired forks and successors (such as CanCanCan) that continue to be widely used in Rails projects.

Service Oriented Container (SOC) focused on creating and managing Services using annotations. Implements lighweight SOA using JEE, JAVA and Ruby. More than 20 services are included (ESB (Mule), jBPM, Jetty, JMS, GWT, DB, Rules, JMX, Spring support..)