Results for param-store

Parameter store for secrets

Easy switch in between ENV and AWS Parameter Store (SSM)

Dynamically stores, parses and providers params. Uses module local readers.

Store for seo params

A rack middleware that searches for UTM tags in the request params, and stores them in cookies for later use.

rack-indifferent monkey patches Rack::Utils::KeySpaceConstrainedParams to make the hash it stores params in support indifferent access. So web frameworks that use rack-indifferent don't have to make a deep copy of the params to allow indifferent access to the params.

Strong params can end up making your controllers very fat and form objects aren't always the best cure. Tidy Strong Params (TSP) takes inspiration from ActiveModelSerialiers and aims to separate param white-listing from the rest of your controller logic whilst also allowing for flexibility in it's implementation. TSP provides a simple way for storing your list of white-listed params in their own directory, hopefully with minimal overhead

a way to efficiently store ids (i.e., possibly sequential numbers > 0), well suited for params-ecoding. Note that the ids will be sorted and uniqued

Write Through and Read Through caching library inspired by CacheMoney and cache_fu, support ActiveRecord 4.

Sidekiq includes a jobs dependencies mechanism to prevent a job from running before another one when enqueued. But sometime your jobs will be enqueued independently, then for you do not know the job id on which you depend on (you could parse Sidekiq queue, but...) `SidekiqLockableJob` allows you to set some locks ( based on job params ) when a job is enqueued or processed (store in redis), to prevent any other jobs to run if locked ( based on job params ) and will unlock any previously set locks ( based on job params ) when a job is **succesfully** completed.

A simple file-system-based cache wrapper. The main method is 'with_cache( :cache_key=>'something_unique', :timeout_seconds=>(an integer) ){ (...) }' If the given cache key exists and has not timed out, it will return the cached value If not, it will * yield to the given block * store the result of the given block in the cache with the given key * return the result of the given block Required params: * :cache_key=>'some unique string that is valid in a filename' Optional params: * :timeout_seconds => (an integer - default 3600) * :cache_dir => (an absolute path - defaults to RAILS_ROOT/tmp/cache if RAILS_ROOT is defined, otherwise /tmp/cache ) Example usage: @stats_json = Itrigga::Cache::FileCache.with_cache(:cache_key=>'admin_stats.json', :timeout_seconds=>600){ /* some expensive remote API / slow IO call here /* }

Read through caching library inspired by Cache Money, support Sequel 4 Read-Through: Queries by ID or any specified unique key, like `User[params[:id]]` or `User[username: 'bachue@gmail.com']`, will first look in memcache store and then look in the database for the results of that query. If there is a cache miss, it will populate the cache. As objects are created, updated, and deleted, all of the caches are automatically expired.

The cookie_tracker easily synchronizes settings stored in cookies with instance variables of the same name available for use in controllers and views. This gem allows you to declare a hash of parameters along with default values that you wish to be loaded/stored in the user's cookies during each page load. Each parameter will be loaded into it's own instance variable of the same name for easy access in controllers and views. If the parameter is passed in the params[] hash, the new value will automatically be stored in the correct cookie and replace the old or default value. This makes it easy to track various options that a user can select on a page, such as items per page, search queries, and custom display settings. If a user clicks off to another page on your site, their settings will be remembered when they return. You can declare the default cookie lifetime options in an initializer or override them at runtime. If you prefer to use the session store over the cookie jar, there is a method for that as well. You can override the default cookie options by creating an initializer. Visit the github page https://github.com/DanKnox/CookieTracker

No description provided.

No description provided.

No description provided.