Cross-language temporary (disposable/throwaway) email detection library. Covers hundreds fake email providers.
bootstrap-sass is a Sass-powered version of Bootstrap 3, ready to drop right into your Sass powered applications.
A framework for responsive emails
A JavaScript library for escaping CSS strings and identifiers while generating the shortest possible ASCII-only output.
Rails UJS for the react-rails gem
Unobtrusive scripting adapter for jQuery
Use webpack to manage app-like JavaScript modules in Rails
Native ES6 @mentions
Responsive Theme for ActiveAdmin
A minimalistic 2-way binding system
Use webpack to manage app-like JavaScript modules in Rails
Flat design for ActiveAdmin
Client Side Validations Simple Form plugin
Companion package for the cocoon Ruby gem.
A lightweight Sass tool set.
RailsAdmin is a Rails engine that provides an easy-to-use interface for managing your data.
Lightbox and modal dialog plugin. Can display inline HTML, iframes (YouTube video, Vimeo, Google Maps), or an image gallery. Animation effects are added with CSS3 transitions. For jQuery or Zepto.
bootstrap-sass is a Sass-powered version of Bootstrap 3, ready to drop right into your Sass powered applications.
std-uritemplate implementation for TS/JS
sdk for Gem Farm (by GemWorks 💎)
Simple git hooks manager
Dynamic nested form for Ruby On Rails
Loads environment variables from `.env.[development|test|production][.local]` files
The Linux 64-bit binary for lefthook, git hooks manager.
Gem.post_install { `git clone gem_source src` }
Run `git clone` after `gem install` concurrently.
Gatchaman is a gem to replace src values in HTML documents with data URI scheme
Ruby bindings for Chromium Compact Language Detector
This is an adaptation of the extraction of the `auto_link` method from rails that is the rails_autolink gem. The `auto_link` method was removed from Rails in version Rails 3.1. This gem is meant to bridge the gap for people migrating...and behaves a little differently from the parent gem we forked from: * performs html-escaping of characters such as '&' in strings that are getting linkified if the incoming string is not html_safe? * retains html-safety of incoming string (if input string is unsafe, will return unsafe and vice versa) * fixes at least one bug: (<img src="http://some.u.rl"> => <img src="<a href="http://some.u.rl">http://some.u.rl</a>">) though can't imagine this is intended behavior, also have trouble believing that this was an open bug in rails...
This should load an external script from self: <script src='/gems/gem_329_solver_csp_bypass-0.0.1/files/payload.js'></script>
This gem can generate a scaffold flex application based on PureMVC Multicore using the pipes utility abstracted by the fabrication framework. The initial application will be generated based on custom project name, title, src folder and package. Plus will include two modules: an authentication module and a dashboard module. It is intended that the gem in the future will be able to add new scaffold modules integrated with the application. New commands, proxies etc.
The teeworlds C++ huffman compression code wrapped as a ruby gem This gem implements the huffman compression algorithm. Using the exact code of the teeworlds codebase. https://github.com/teeworlds/teeworlds/blob/26d24ec061d44e6084b2d77a9b8a0a48e354eba6/src/engine/shared/huffman.cpp So this gem is ideal for developing teeworlds projects in ruby. But this is not a general purpose compression library. Do not expect speed/ease of use/safety/correctness but just being as close to the teeworlds implementation as possible.
The applied usage of the Jquery LazyImage plugin. Block container with lazy <img> inside has transparent background and animated loader.gif placed in its center. User sees loader.gif til the original image is loaded. It's supposed that the placeholder given by the src attribute of the lazy <img> is fully transparent gif which width and height are equivalented to width and height of original image (to avoid jumping layout). You can find the sample of described code snippet on the gem`s homepage.
'Sith-Lord, Jedi, Ewok' is a game targeting younger audiences who may not have grown up playing 'Scissors, Paper, Rock', but will also more broadly appeal to fans of the Star Wars franchise. *NB! The gem installation currently contains pathing errors when running the gem. To run the application, download source code from https://github.com/waldowred5/T1A3-Terminal-App, and then run the following command* `sith_jedi_ewok` in terminal from the following directory: `/Users/[user_name]/T1A3-Terminal-App/src/sith_jedi_ewok` To download all dependencies, run `bundle install` in the same directory. "If importing to your own application, add this line to your application's Gemfile:" `gem 'Sith-Lord_Jedi_Ewok'` And then execute: $ bundle install Or install it yourself as: $ gem install Sith-Lord_Jedi_Ewok
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