Automated module to fetch all your 3rd party binaries to power your nodejs applications
plugin to use the camera and get binary
Utility for downloading artifacts from different versions of Electron
List of binary file extensions
Check if a file path is a binary file
Get the version of a binary in semver format
Get a stream as a string, Buffer, ArrayBuffer or array
SDK for building AI agents with Claude Code's capabilities. Programmatically interact with Claude to build autonomous agents that can understand codebases, edit files, and execute workflows.
Simple to use, blazing fast and thoroughly tested websocket client and server for Node.js
Check whether a binary version satisfies a semver range
The linux x64 distribution of the Sentry CLI binary.
Helper function to build binary assignment operator visitors
Get binary gap for given input
C APIs for registering a Node-API module exporting an interface for invoking a binary numerical function.
Parse binary files with a schema into nicely readable objects
Various helper utilities for working with buffers and binary data
read and write binary structures and data types
Command-Line Interface for Firebase
The Linux 64-bit binary for esbuild, a JavaScript bundler.
The linux arm64 distribution of the Sentry CLI binary.
> Rewrite a WASM binary
High-performance (binary) tree and sorted map implementation (AVL, Splay, Radix, Red-Black)
Conversion of JavaScript primitives to and from Buffer with binary order matching natural primitive order
High-performance JSON serialization library
user_preference is a small library for setting and getting categorized user preferences. Supports both binary and multivalue preferences and default values.
Get the git revision of a given repository. Does not require Git binaries
KyotoTycoon binary access module, supports get(bulk), set(bulk), remove(bulk), and play LUA script.
Not all things in this world may be blessed with lovely ascii art, json, yaml, and other funky formats. Sometimes you need to get your arms dirty with some raw unadulterated binary! Binary needn't scar you for life though - so here's my little ORM for bits of binary.
The docker-nsenter plugin allows you to use the nsenter binary on your host or the Vagrant proxy VM to run commands or get a shell in Vagrant-managed Docker containers.
This is a very trivial implementation of an interface for Image Magick. It relies on the binaries for Image Magic (identify and convert) to be available on the system, and to be in the $PATH. I wrote this for my spouse, who needed to resize scanned artwork for various art websites, such as 'etsy', 'artpal', and 'art.com'. check out the readme on the github homepage for this gem, to get details on usage and limitations.
Implements a gateway server to allow barebone basic sensor components to report state change updates as simple via TCP/UDP ports without the 'overhead' of the HTTP protocol. A power sensor for example might just broadcast a four byte floating point binary number once every second to an UDP port or an arduino board sends a UDP datagram whenever a button is pushed. You get the idea, this is how to bring embedded devices into the world of HTTP and Javascript...
= id3lib-ruby id3lib-ruby provides a Ruby interface to the id3lib C++ library for easily editing ID3 tags (v1 and v2) of MP3 audio files. The class documentation starts at ID3Lib::Tag. == Features * Read and write ID3v1 and ID3v2 tags * Simple interface for adding, changing and removing frames * Quick access to common text frames like title and performer * Custom data frames like attached picture (APIC) * Pretty complete coverage of id3lib's features * UTF-16 support (warning: id3lib writes broken UTF-16 frames) * Windows binary gem available The CHANGES file contains a list of changes between versions. == Installation See INSTALL. == Online Information The home of id3lib-ruby is http://id3lib-ruby.rubyforge.org == Usage require 'rubygems' require 'id3lib' # Load a tag from a file tag = ID3Lib::Tag.new('talk.mp3') # Get and set text frames with convenience methods tag.title #=> "Talk" tag.album = 'X&Y' tag.track = '5/13' # Tag is a subclass of Array and each frame is a Hash tag[0] #=> { :id => :TPE1, :textenc => 0, :text => "Coldplay" } # Get the number of frames tag.length #=> 7 # Remove all comment frames tag.delete_if{ |frame| frame[:id] == :COMM } # Get info about APIC frame to see which fields are allowed ID3Lib::Info.frame(:APIC) #=> [ 2, :APIC, "Attached picture", #=> [:textenc, :mimetype, :picturetype, :description, :data] ] # Add an attached picture frame cover = { :id => :APIC, :mimetype => 'image/jpeg', :picturetype => 3, :description => 'A pretty picture', :textenc => 0, :data => File.read('cover.jpg') } tag << cover # Last but not least, apply changes tag.update! == Licence This library has Ruby's licence: http://www.ruby-lang.org/en/LICENSE.txt == Author Robin Stocker <robinstocker at rubyforge.org>
Log2json lets you read, filter and send logs as JSON objects via Unix pipes. It is inspired by Logstash, and is meant to be compatible with it at the JSON event/record level so that it can easily work with Kibana. Reading logs is done via a shell script(eg, `tail`) running in its own process. You then configure(see the `syslog2json` or the `nginxlog2json` script for examples) and run your filters in Ruby using the `Log2Json` module and its contained helper classes. `Log2Json` reads from stdin the logs(one log record per line), parses the log lines into JSON records, and then serializes and writes the records to stdout, which then can be piped to another process for processing or sending it to somewhere else. Currently, Log2json ships with a `tail-log` script that can be run as the input process. It's the same as using the Linux `tail` utility with the `-v -F` options except that it also tracks the positions(as the numbers of lines read from the beginning of the files) in a few files in the file system so that if the input process is interrupted, it can continue reading from where it left off next time if the files had been followed. This feature is similar to the sincedb feature in Logstash's file input. Note: If you don't need the tracking feature(ie, you are fine with always tailling from the end of file with `-v -F -n0`), then you can just use the `tail` utility that comes with your Linux distribution.(Or more specifically, the `tail` from the GNU coreutils). Other versions of the `tail` utility may also work, but are not tested. The input protocol expected by Log2json is very simple and documented in the source code. ** The `tail-log` script uses a patched version of `tail` from the GNU coreutils package. A binary of the `tail` utility compiled for Ubuntu 12.04 LTS is included with the Log2json gem. If the binary doesn't work for your distribution, then you'll need to get GNU coreutils-8.13, apply the patch(it can be found in the src/ directory of the installed gem), and then replace the bin/tail binary in the directory of the installed gem with your version of the binary. ** P.S. If you know of a way to configure and compile ONLY the tail program in coreutils, please let me know! The reason I'm not building tail post gem installation is that it takes too long to configure && make because that actually builds every utilties in coreutils. For shipping logs to Redis, there's the `lines2redis` script that can be used as the output process in the pipe. For shipping logs from Redis to ElasticSearch, Log2json provides a `redis2es` script. Finally here's an example of Log2json in action: From a client machine: tail-log /var/log/{sys,mail}log /var/log/{kern,auth}.log | syslog2json | queue=jsonlogs \ flush_size=20 \ flush_interval=30 \ lines2redis host.to.redis.server 6379 0 # use redis DB 0 On the Redis server: redis_queue=jsonlogs redis2es host.to.es.server Resources that help writing log2json filters: - look at log2json.rb source and example filters - http://grokdebug.herokuapp.com/ - http://www.ruby-doc.org/stdlib-1.9.3/libdoc/date/rdoc/DateTime.html#method-i-strftime
Log2json lets you read, filter and send logs as JSON objects via Unix pipes. It is inspired by Logstash, and is meant to be compatible with it at the JSON event/record level so that it can easily work with Kibana. Reading logs is done via a shell script(eg, `tail`) running in its own process. You then configure(see the `syslog2json` or the `nginxlog2json` script for examples) and run your filters in Ruby using the `Log2Json` module and its contained helper classes. `Log2Json` reads from stdin the logs(one log record per line), parses the log lines into JSON records, and then serializes and writes the records to stdout, which then can be piped to another process for processing or sending it to somewhere else. Currently, Log2json ships with a `tail-log` script that can be run as the input process. It's the same as using the Linux `tail` utility with the `-v -F` options except that it also tracks the positions(as the numbers of lines read from the beginning of the files) in a few files in the file system so that if the input process is interrupted, it can continue reading from where it left off next time if the files had been followed. This feature is similar to the sincedb feature in Logstash's file input. Note: If you don't need the tracking feature(ie, you are fine with always tailling from the end of file with `-v -F -n0`), then you can just use the `tail` utility that comes with your Linux distribution.(Or more specifically, the `tail` from the GNU coreutils). Other versions of the `tail` utility may also work, but are not tested. The input protocol expected by Log2json is very simple and documented in the source code. ** The `tail-log` script uses a patched version of `tail` from the GNU coreutils package. A binary of the `tail` utility compiled for Ubuntu 12.04 LTS is included with the Log2json gem. If the binary doesn't work for your distribution, then you'll need to get GNU coreutils-8.13, apply the patch(it can be found in the src/ directory of the installed gem), and then replace the bin/tail binary in the directory of the installed gem with your version of the binary. ** P.S. If you know of a way to configure and compile ONLY the tail program in coreutils, please let me know! The reason I'm not building tail post gem installation is that it takes too long to configure && make because that actually builds every utilties in coreutils. For shipping logs to Redis, there's the `lines2redis` script that can be used as the output process in the pipe. For shipping logs from Redis to ElasticSearch, Log2json provides a `redis2es` script. Finally here's an example of Log2json in action: From a client machine: tail-log /var/log/{sys,mail}log /var/log/{kern,auth}.log | syslog2json | queue=jsonlogs \ flush_size=20 \ flush_interval=30 \ lines2redis host.to.redis.server 6379 0 # use redis DB 0 On the Redis server: redis_queue=jsonlogs redis2es host.to.es.server Resources that help writing log2json filters: - look at log2json.rb source and example filters - http://grokdebug.herokuapp.com/ - http://www.ruby-doc.org/stdlib-1.9.3/libdoc/date/rdoc/DateTime.html#method-i-strftime
lithos is a self-contained embedded key-value store written from scratch as a native extension — no external database dependency. It uses a log-structured merge (LSM) tree: a write-ahead log makes every write durable, an in-memory sorted memtable flushes to immutable SSTables (with bloom filters), and compaction merges them. Keys and values are arbitrary binary strings; keys are kept in sorted order so you get ordered iteration and range scans, plus crash recovery via WAL replay. Windows MSVC (mswin) Ruby only.
Wish you could write your Ruby in XML? Has the fact that Ruby is not "enterprise" got you down? Do you feel like your Ruby code could be made to be more "scalable"? Well look no further my friend. You've found the enterprise gem. Once you install this gem, you too can make Rails scale, Ruby faster, your code more attractive, *and* have more XML in your life. I'm sure you're asking yourself, "how can the enterprise gem promise so much?". Well the answer is easy, through the magic of XML! The enterprise gem allows you to write your Ruby code in XML, therefore making your Ruby and Rails code scale. Benefits of writing your code in XML include: * It's easy to read! * It scales! * Cross platform * TRANSFORM! your code using XSLT! * Search your AST with XPath *or* CSS! The enterprise gem even comes with a handy "enterprise" binary to help you start converting your existing *legacy* Ruby code in to scaleable, easy to read XML files. Let's start getting rid of that nasty Ruby code and replacing it with XML today!
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.