Modern and scalable routing for React applications
Firebase JavaScript library for web and Node.js
Isomorphic Javascript SDK for Supabase
Implements performance.now (based on process.hrtime).
userland implementation of https://github.com/joyent/node/issues/5243
process.hrtime() to words
Isomorphic storage client for Supabase.
Official React Native Tracking Library for Mixpanel Analytics
Modern and scalable routing for React applications
Simple key-value storage with support for multiple backends
Official React Native SDK
A logger for just about everything.
Cloud Storage Client Library for Node.js
Microsoft Azure Storage SDK for JavaScript - Blob
Shim for process.hrtime in the browser
Fast, small, efficient JavaScript memoization lib to memoize JS functions
Invoke scoped data storage for AWS Lambda Node.js Runtime Environment
OAuth 1.0a Request Authorization for Node and Browser.
IBM SDK for JavaScript
Parquet file parser for JavaScript
The Firebase Firestore compatibility package
This is the Cloud Storage component of the Firebase JS SDK.
An exchange for managing authentication and token refresh in urql
High Performance Layer 1 / Layer 2 Caching with Keyv Storage
Backend components to the ACPC Poker GUI Client. Includes a player that saves states from the dealer to persistent storage, and components to start, stop, and manage match components.
Dead Simple CMS is a library for modifying different parts of your website without the overhead of having a fullblown CMS. The idea with this library is simple: provide an easy way to hook into different parts of your application (not only views) by defining the different parts to modify in an easy, straight-forward DSL. The basic components of this library include: * A DSL to define the changeable values in your app * Form generators based on SimpleForm (with or without Bootstrap) and default rails FormBuilder * Expandable storage mechanisms so you can store the data in different locations * Currently supported: Redis, Database, Memcache, even Memory (for testing) * Presenters/renderers so you can take groups of variables and render them into your views (ie image_tag) What it doesn't have: * Versioning - be able to look at old versions of the content * Timing - set start and end time for different content * Page builder tools - this is not the right tool if you want to design full pages
= ebs_conductor The EBS Conductor is a library for managing Amazon Elastic Block Storage volumes and snapshots. It is designed to persist a specific set of data (a "lineage") between different compute instances. EBS Conductor can be used on it's own, but it's most powerful when executed on an EC2 instance using Chef, and the ebs_conductor cookbook[https://github.com/rgeyer/cookbooks/tree/master/cookbooks/ebs_conductor] == Examples === Attach a new 1GB blan volume in the lineage "foobar" to a linux box at /dev/sdb1 ebs_conductor = Rgeyer::Gem::EbsConductor.new('...','...') ebs_conductor.attach_from_lineage('i-abcd1234', 'foobar', 1, '/dev/sdb1') === Attach a specific snapshot to a 1GB volume in the lineage "foobar" to a linux box at /devb/sdb1 ebs_conductor = Rgeyer::Gem::EbsConductor.new('...','...') ebs_conductor.attach_from_lineage('i-abcd1234', 'foobar', 1, '/dev/sdb1' {:snapshot_id => 'snap-abcd1234'}) === Snapshot the lineage "foobar", do not purge any old snapshots in the lineage ebs_conductor = Rgeyer::Gem::EbsConductor.new('...','...') ebs_conductor.snapshot_lineage('foobar') === Snapshot the lineage "foobar", and purge old snapshots so that only 7 remain ebs_conductor = Rgeyer::Gem::EbsConductor.new('...','...') ebs_conductor.snapshot_lineage('foobar', {:history_to_keep => 7}) === Snapshot the lineage "foobar" from the specified volume_id This is useful if you're trying to start a lineage from a "naked" instance, or if you are trying to create a new lineage from an existing one ebs_conductor = Rgeyer::Gem::EbsConductor.new('...','...') ebs_conductor.snapshot_lineage('foobar', {:history_to_keep => 7, :volume_id => 'vol-abcd1234'}) == List of To Do Items * Support for stripes in a lineage == Copyright Copyright (c) 2011 Ryan Geyer. See LICENSE.txt for further details.
== Medusa: a ruby crawler framework {rdoc-image:https://badge.fury.io/rb/medusa-crawler.svg}[https://rubygems.org/gems/medusa-crawler] rdoc-image:https://github.com/brutuscat/medusa-crawler/workflows/Ruby/badge.svg?event=push Medusa is a framework for the ruby language to crawl and collect useful information about the pages it visits. It is versatile, allowing you to write your own specialized tasks quickly and easily. === Features * Choose the links to follow on each page with +focus_crawl+ * Multi-threaded design for high performance * Tracks +301+ HTTP redirects * Allows exclusion of URLs based on regular expressions * Records response time for each page * Obey _robots.txt_ directives (optional, but recommended) * In-memory or persistent storage of pages during crawl, provided by Moneta[https://github.com/moneta-rb/moneta] * Inherits OpenURI behavior (redirects, automatic charset and encoding detection, proxy configuration options). <b>Do you have an idea or a suggestion? {Open an issue and talk about it}[https://github.com/brutuscat/medusa-crawler/issues/new]</b> === Examples Medusa is versatile and to be used programatically, you can start with one or multiple URIs: require 'medusa' Medusa.crawl('https://www.example.com', depth_limit: 2) Or you can pass a block and it will yield the crawler back, to manage configuration or drive its crawling focus: require 'medusa' Medusa.crawl('https://www.example.com', depth_limit: 2) do |crawler| crawler.discard_page_bodies = some_flag # Persist all the pages state across crawl-runs. crawler.clear_on_startup = false crawler.storage = Medusa::Storage.Moneta(:Redis, 'redis://redis.host.name:6379/0') crawler.skip_links_like(/private/) crawler.on_pages_like(/public/) do |page| logger.debug "[public page] #{page.url} took #{page.response_time} found #{page.links.count}" end # Use an arbitrary logic, page by page, to continue customize the crawling. crawler.focus_crawl(/public/) do |page| page.links.first end end
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.