Results for mais-utils

Dotfiles Manager

Ruby wrapper for the Torque C library utilizing Ruby-FFI. This has been successfully tested with Torque 4.2.10 and greater. Your mileage may vary.

Set-like wrapper around GNU comm and related textfile utilities. A common use case is to identify differences between exported datasets where the datasets may exceed 100K rows and each row may exceed 4K characters.

Provides util methods available to all RSpec test automation projects. Util methods include additional Ruby functionality, along with RSpec helper methods. May include data-driven automation helpers in the future.

A collection of framework-agnostic tools and utilities for Rodauth, including database migration helpers, table inspection, and possibly... less (this is an active development area, experimental stuff that may come and go).

Olag is Oren's set of utilities for creating a well-behaved gem. This is very opinionated software; it eliminates a lot of the boilerplate, at the cost of making many decisions which may not be suitable for everyone (directory structure, code verification, codnar for documentation, etc.).

yarv-prof does nothing special to profile YARV behavior, just heavily depends on Ruby's DTrace probes support. If you are looking for something useful to utilize Ruby's DTrace feature, yarv-prof may work for you.

This tool helps visualize which directories are occupying the most storage. Any directory that occupies more than 5% of used disk space is added to a visual hierarchichal storage report in the form of a Google Sankey diagram. The storage data is gathered using the linux `du` utility. It has been tested on Mac OSX and linux systems (Ubuntu & CentOS), will not work on Windows. Run as sudo if analyzing otherwise inaccessible directories. May take a while to run.

Sometimes, you might want your HTML to include a one-off image file that is just for one person. Making this file public may be undesireable for security reasons, or perhaps simply because it is not worth the overhead of multiple HTTP requests. This gem provides a utility method that takes a locally-saved image file, perhaps within your non-public tmp directory, encodes it as Base64, and returns an HTML <img> element with the correct data URL attributes. It is made possible by the RFC 2397 scheme, which is now fairly well supported in modern browsers.

The dep_walker is small utility gem that checks dependencies for native extensions used by installed gems on Windows. If you are {RubyInstaller}[http://www.rubyinstaller.org] user and have seen message box: <em>"This application has failed to start because <name_of_dll>.dll was not found. Re-installing the application may fix this problem"</em> when you tried to use gem that has pre-built binariy extension, you've faced common problem on Windows systems - missing dependency dll. Same error might occur even if extension library was built during gem installation if all header files and libraries are available to the build tools, but runtime dependencies are not present. With dep_walker you can simply check all installed gems. Even more, if log is turned on, gem will print out information where dependency is found on the system, so you can check whether Ruby extension really uses correct version of required dll.

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 &amp;&amp; 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

Svnbranch is a program that can assist with managing Subversion branches. Svnbranch allows users to easily create new software branches, and merge in changes from a different repository branch. Using branches in software development is a key concept in managing large projects. Indeed, the GIT source code management package provides an incredibly easy way to manage branches, and branch use is greatly encouraged by several large FOSS projects, for instance the Linux kernel. Svnbranch attempts to offer the same level of user-friendliness to Subversion users. Subversion does branching very well, but its syntax escapes many, or is downright long and tedious. Instead of typing in long, error-prone svn commands, Svnbranch abstracts one layer above the Subversion command line utility providing simple command syntax for common use cases. The result is that with more powerful tools, developers may take advantage of the benefits of branched development practices.

No description provided.

No description provided.

No description provided.