Update a copyright statement with the current year. Also makes minor corrections.
Validate, add and update copyright headers automatically, based on the git history.
Update copyright information in a MIT license.
Validate, add and update copyright headers automatically, based on the git history.
Tiny utility to update copyright years or ranges automatically in the DOM.
A polyfill for the internal diagnostics_channel module
Automatically update copyright years in website footers.
list of SPDX standard license exceptions
Color helpers to ease transformation between formats, gamut, etc
This is a pure-js JSON streaming parser for node.js
CLI tool to update caniuse-lite to refresh target browsers from Browserslist config
DES implementation
@intlify/core-base
@intlify/message-compiler
Algorithm for finding the root of a yarn workspace, extracted from yarnpkg.com
TypeScript definition for strtok3 token
Runtime library for code generated by the protoc plugin "protobuf-ts"
Attaches timezone to Snowplow events
Fork pseudoterminals in Node.JS
Testmo command line interface
Testcontainers is a NodeJS library that supports tests, providing lightweight, throwaway instances of common databases, Selenium web browsers, or anything else that can run in a Docker container
A lightweight graphic library providing 2d draw for Apache ECharts
@intlify/shared
Write buffer
Automatically updates the year for the copyright line on the bottom of your site. Dynamically inputs your name or company
github-copywriter scans through your repositories and updates any copyrights it finds.
Gem creates methods for application which display date and copyright info
Automatically update copyright messages using git
"This gem adds a copyright to your page. The year updates itself. All you need to do is add your name and message."
Copyright generator which automatically updates the year, allows you to put in your name and a message.
Customize and have your copyright section update automatically with each year change in your rails app. Provides the ability to attach a short message and insert website name to explicity state and render a copyright symbol along with it.
# Eschaton for Ruby An attempt to adapt the game of Eschaton, from David Foster Wallace's [*Infinite Jest*](http://en.wikipedia.org/wiki/Infinite_Jest), into a text-based Ruby game. Definitely a work in progress. Not much to look at now, but I'll update the README when the game gets a little more involved. To install: gem install eschaton To play: eschaton License ---- MIT Copyright (c) 2014, Sean Parr Eschaton is provided as-is under the MIT license. For more information see LICENSE.
= sql_valued_columns SqlValuedColumns is an ActiveRecord plugin that will let you have specific SQL statements executed on INSERT / UPDATE. It will call the SQL function you provide, passing the arguments specified in the call to sql_column. See the documentation for SqlValuedColumns::ClassMethods#sql_column for more information regarding usage, including passing Strings and Proc objects as arguments to your SQL function. Example: You have a model with two columns, one named "another_column" and the other named "size_of_another_column". Whenever you insert data into "another_column", you want to have size_of_another_column have the result of the SQL function LENGTH inserted into it. class MyModel < ActiveRecord::Base sql_column :size_of_another_column, "LENGTH", :another_column end Example 2: You have a model with three columns, position, latitude and longitude. Latitude and longitude are values expressed as angles, and position is a special datatype for your database that represents the X/Y/Z projection of that particular latitude and longitude (example: http://www.postgresql.org/docs/8.3/static/earthdistance.html ) When you insert data with latitude and longitude, you want to automatically call a function in your database to transform the latitude and longitude into the appropriate represenation. class MyModel < ActiveRecord::Base sql_column :position, "ll_to_earth", :latitude, :longitude end Example 3: You are an insane criminal who has somehow learned SQL. You would like to make anyone who runs your code to suffer database punishing queries and odd security and data formatting issues that will make them rue the day they ever learned of computers. class MyModel < ActiveRecord::Base sql_column :a_column, "(SELECT count(id) FROM large_list_of_things)", :raw => true sql_column :another_column, '(SELECT count(other_id) FROM other_large_list_of_things WHERE some_column = \'#{some_model_method}\')', :raw => true end == Notes No tests yet, am lazy. == Copyright Copyright (c) 2009 Chris Zelenak. See LICENSE for details.
== coral This gem is simply a meta package that installs and requires the CORL gem. Note: CORL is still early in development! DO NOT USE IN PRODUCTION YET!! Now you get to hear the story of two names. Short story first; We switched to the CORL name (github.com/coralnexus/corl). If your interested in why: The original name of the CORL project was Coral, and we were exited when we found the Ruby gem name "coral" available. Our first versions of our CORL system were named coral_core, coral_cloud, coral_vagrant, coral_plan, and many more were planned. We created a meta gem (this one) to install a core combination of gems. During the course of development we found another project that came before ours that uses the name coral, so we decided to update our project name, so as to avoid conflicts. For us Coral is more than a word, it is a concept that embodies dynamic ecosystems supporting a rich variety of lifeforms. Coral are very interesting creatures and we endeavor to create software that helps build dynamic ecosystems of digital creatures. We decided to use an acronym that sounds like the word Coral because the acronym fit with our desire to create something good for administration but also good for flexible research, so we came to Cluster Orchestration and Research Library. We split the core components out into a small concurrent plugin framework called Nucleon, upon which CORL is built. All of our coral sub gems are integrated into these two. This gem exists only as a installer for people who accidentally spell coral the right way when trying to install the CORL system. Use the CORL gem instead. == Copyright Licensed under Apache license, version 2. See LICENSE.txt for further details. Copyright (c) 2013-2014 Adrian Webb <adrian.webb@coralnexus.com> Coral Technology Group LLC
= DESCRIPTION: Provides a Chef handler which can report run status, including any changes that were made, to a rabbit server. In the case of failed runs a backtrace will be included in the details reported. Based on the Graylog Gelf handler by Jon Wood (<jon@blankpad.net>) https://github.com/jellybob/chef-gelf = REQUIREMENTS: * A Rabbit server running somewhere. = USAGE: This example makes of the chef_handler cookbook, place some thing like this in cookbooks/chef_handler/recipes/rabbit.rb and add it to your run list. include_recipe "chef_handler::default" gem_package "chef-rabbit" do action :nothing end.run_action(:install) # Make sure the newly installed Gem is loaded. Gem.clear_paths require 'chef/rabbit' chef_handler "Chef::RABBIT::Handler" do source "chef/rabbit" arguments({ :connection => { :host => "your_rabbit_server", :user => "rabbit_user", :pass => "rabbit_pass", :vhost => "/stuff" } :queue => { :name => "some_queue", :params => { :durable => true, ... } }, :exchange => { :name => "some_exchange", :params => { :durable => true, ... } }, :timestamp_tag => "@timestamp" }) supports :exception => true, :report => true end.run_action(:enable) Arguments take the form of an options hash, with the following options: * :connection - http://rubybunny.info/articles/connecting.html * :queue - rabbit queue info to use. name is set to "chef-client" + durable = true by default * :exchange - rabbit exchange to use .default_exchange + durable = true by default * :timestamp_tag - tag for timestamp "timestamp" by default * :blacklist ({}) - A hash of cookbooks, resources and actions to ignore in the change list. = BLACKLISTING: Some resources report themselves as having updated on every run even if nothing changed, or are just things you don't care about. To reduce the amount of noise in your logs these can be ignored by providing a blacklist. In this example we don't want to be told about the GELF handler being activated: chef_handler "Chef::RABBIT::Handler" do source "chef/rabbit" arguments({ :blacklist => { "chef_handler" => { "chef_handler" => [ "nothing", "enable" ] } } }) supports :exception => true, :report => true end.run_action(:enable) = LICENSE and AUTHOR: Copyright 2014 by MTN Satellite Communications Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
= DESCRIPTION: Provides a Chef handler which can report run status, including any changes that were made, to a Graylog2 server. In the case of failed runs a backtrace will be included in the details reported. = REQUIREMENTS: * A Graylog2 server running somewhere. = USAGE: This example makes of the chef_handler cookbook, place some thing like this in cookbooks/chef_handler/recipes/gelf.rb and add it to your run list. It also assumes your Graylog2 server has set the attribute rsyslog_server to true. log_server = search(:node, "rsyslog_server:true").first if log_server include_recipe "chef_handler::default" gem_package "chef-gelf" do action :nothing end.run_action(:install) # Make sure the newly installed Gem is loaded. Gem.clear_paths require 'chef/gelf' chef_handler "Chef::GELF::Handler" do source "chef/gelf" arguments({ :server => log_server['fqdn'] }) supports :exception => true, :report => true end.run_action(:enable) end Arguments take the form of an options hash, with the following options: * :server - The server to send messages to. * :port (12201) - The port to send on. * :facility (chef-client) - The facility to report under. * :host (node.fqdn) - The host to report messages as coming from. * :blacklist ({}) - A hash of cookbooks, resources and actions to ignore in the change list. = BLACKLISTING: Some resources report themselves as having updated on every run even if nothing changed, or are just things you don't care about. To reduce the amount of noise in your logs these can be ignored by providing a blacklist. In this example we don't want to be told about the GELF handler being activated: chef_handler "Chef::GELF::Handler" do source "chef/gelf" arguments({ :server => log_server['fqdn'], :blacklist => { "chef_handler" => { "chef_handler" => [ "nothing", "enable" ] } } }) supports :exception => true, :report => true end.run_action(:enable) = LICENSE and AUTHOR: Author:: Jon Wood (<jon@blankpad.net>) Copyright:: 2011, Blank Pad Development Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.