> If you want to load configurations, pls go to [cosmiconfig](https://github.com/davidtheclark/cosmiconfig)
Just run this on the folder where a browserlist config exists.
Check if a path exists
Ultra-low latency data at the edge
Synchronous validation of a path existing either as a file or as a directory.
A Metro config for running React Native projects with the Metro bundler
Get the first path that exists on disk of multiple paths
Provides functions for detecting if the host environment supports the WebCrypto API
Just run this on the folder where a browserlist config exists.
Drop-in replacement for `fs.existsSync` with zero dependencies. Other libs I found either have crucial differences from fs.existsSync, or unnecessary dependencies. See README.md for more info.
Find the first config file matching a given name in the current directory or the nearest ancestor directory.
Test whether a path exists on the filesystem.
Shared configuration utilities for Herb tools
Redis commands
A wrapper on top of kleur with ability to write test against the color functions
A ridiculously light-weight argument validator (now browser friendly)
Types for the TypeScript-ESTree AST spec
Get the first fulfilled promise that satisfies the provided testing function
check whether a command line command exists in the current environment
Microsoft Application Insights Web Snippet
Recursively mkdir, like `mkdir -p`
Just like `fs.exists` and `fs.existsSync`, but cached
TypeScript definitions for command-exists
Checks whether a command line command exists in the current environment.
Getting information about the current Ruby environment can be a bit arcane. Lots of solutions exist in the form of various globals, things like Config::CONFIG, and various other oddities. This gem tries to bring it all together and make it sane.
RTA Log Manager has been designed and implemented to provide standard logging API for developers.This prevents chaos in log data format. Also provide multiple extendable log repositories including wrapping existing loggers, like 'Fluentd' or implement completely new custom logger. All main features of log manager are configeable through a json config file.
Bring browserslist to Ruby. Use your existing browserslist config and convert it to a Ruby hash for use with Rails allowed browsers or other browser support detection.
Tattle is a little reporting script used for collecting system information from the Ruby community. The purpose is to help implementors of Ruby and its libraries to better understand the install footprint of the community at large. After installing the gem, you can simply run "tattle" to help add to the existing data available. Tattle sends information from Config::CONFIG to a central server which aggregates and reports the data received.
Packrat is a Sinantra extension based around the idea of mixing and matching. With Packrat we can combine multiple Sinatra applications into one instance, where they can share configuration data, filters, css and other static assets. Creating a new site out of existing pieces should be as simple as cloning a series of pieces, and for each one, adding one line to a config file.
HAST stands for 'Hosting Account Status Tool'. HAST is a tool for fetching domains from Apache configuration files and from Postfix on a hosting server environment. It will then run a report, checking the DNS records for each domain to see if they match your server. This is important for finding "dead" domains where the domain either doesn't exist anymore or where the owner have moved it to another hosting provider. Before you can use HAST, you need to setup a config.yml file. Run 'hast --generate-config > config.yml' to create a sample config file that you can modify.
Generates rake tasks for backing up and restoring your database and public folder (which should also contain any user uploaded assets) to and from an existing bucket in your Amazon S3 account. The rake tasks compresses and uploads each backup with a time stamp and the config file allows you to set how many of each backup to keep. Additionally, the plugin can be configured to generate and send a backup status report via email.
SpreePiwik ========== Adds piwik tracking with Ecommerce tracking Status ------ [](https://travis-ci.org/berkes/spree_piwik) [](https://codeclimate.com/github/berkes/spree_piwik) Installation ------------ Add spree_piwik to your Gemfile: ```ruby gem 'spree_piwik' ``` Bundle your dependencies and run the installation generator: ```shell bundle bundle exec rails g spree_piwik:install ``` Add your Piwik URL and site-id to the `config/initializers/spree_piwik.rb` For example: ```ruby Spree::Piwik::Config[:piwik_url] = "piwik.example.com" Spree::Piwik::Config[:piwik_id] = 1337 ``` Will use http(s)://piwik.example.com/ as url for your Piwik. And track stats for the site that has the id 1337 in Piwik. Screenshot ---------- . Testing ------- First bundle your dependencies, then run `rake`. `rake` will default to building the dummy app if it does not exist, then it will run specs. The dummy app can be regenerated by using `rake test_app`. ```shell bundle bundle exec rake ``` When testing your applications integration with this extension you may use it's factories. Simply add this require statement to your spec_helper: License ------- SpreePiwik is released under the [New BSD License](https://github.com/spree/spree/blob/master/license.md) similar to Spree.
If you are a guy who always find something wrong only after sending a pull requset, Priha will help you because Priha lets you examine files' diff between the parent branch and HEAD of the current branch in a real GitHub pull request. However, DO NOT use Priha for your secret repostitory. Since Priha pushes some commits to another repository on GitHub, it easily cause a security incident, espacially the branch you set for Priha is "public". Also, Priha removes all branches on the repository specified in config, so you MUST create a new repository for this purpose and DO NOT use the existing one.
By default, if a page or a post in a Jekyll site has a syntax error in the front matter, Jekyll logs an error, does not render anything for the given page, and continues. The result is a site without any content for the page with the syntax error. This can be confusing for people who build sites without looking at the CLI, such as those of us whose sites build in a CI. In these cases, we may wish for our build to fail if there are front matter syntax errors. [This PR](https://github.com/jekyll/jekyll/pull/5832/files) seeks to add a config option for that, but in the meantime this plugin exists to fill the gap. This plugin may also be used to add the option to sites using an older version of Jekyll.
==== Topic Maps for Rails (rtm-rails) RTM-Rails is the Rails-Adapter for Ruby Topic Maps. It allows simple configuration of topicmaps in config/topicmaps.yml. ==== Overview From a developer's perspective, RTM is a schema-less database management system. The Topic Maps standard (described below) on which RTM is based provides a way of creating a self-describing schema just by using it. You can use RTM as a complement data storage to ActiveRecord in your Rails apps. ==== Quickstart - existing Rails project jruby script/generate topicmaps Run the command above after installing rtm-rails. This will create * a minimal default configuration: config/topicmaps.yml and * a file with more examples and explanations config/topicmaps.example.yml * a file README.topicmaps.txt which contains more information how to use it and where to find more information * an initializer to load the topicmaps at startup * a rake task to migrate the topic maps backends in your rails application. ==== Quickstart - new Rails project For a new Rails application these are the complete initial steps: jruby -S rails my_topicmaps_app cd my_topicmaps_app jruby -S script/generate jdbc jruby -S script/generate topicmaps # The following lines are necessary because Rails does not have a template # for the H2 database and Ontopia does not support the Rails default SQLite3. sed -e "s/sqlite3/h2/" config/database.yml > config/database.yml.h2 mv config/database.yml.h2 config/database.yml # Prepare the database and then check if all is OK jruby -S rake topicmaps:migrate_backends jruby -S rake topicmaps:check ==== Usage inside the application When everything is fine, let's create our first topic: jruby -S script/console TM[:example].get!("http://example.org/my/first/topic") # and save the topic map TM[:example].commit Access the configured topic maps anywhere in your application like this: TM[:example] To retrieve all topics, you can do TM[:example].topics To retrieve a specific topic by its subject identifier: TM[:example].get("http://example.org/my/topic") Commit the changes to the database permanently: TM[:example].commit ... or abort the transaction: TM[:example].abort More information can be found on http://rtm.topicmapslab.de/ ==== Minimal configuration default: topicmaps: example: http://rtm.topicmapslab.de/example1/ The minimal configuration creates a single topic map, named :example with the locator given. This topic map will be persisted in the same database as your ActiveRecord connection if not specified otherwise. The default backend is OntopiaRDBMS (from the rtm-ontopia gem). A more complete configuration can be found in config/topicmaps.example.yml after running "jruby script/generate topicmaps". It also includes how to specifiy multiple connections to different data stores and so on. ==== Topic Maps Topic Maps is an international industry standard (ISO13250) for interchangeably representing information about the structure of information resources used to define topics, and the relationships between topics. A set of one or more interrelated documents that employs the notation defined by this International Standard is called a topic map. A topic map defines a multidimensional topic space - a space in which the locations are topics, and in which the distances between topics are measurable in terms of the number of intervening topics which must be visited in order to get from one topic to another, and the kinds of relationships that define the path from one topic to another, if any, through the intervening topics, if any. In addition, information objects can have properties, as well as values for those properties, assigned to them. The Topic Maps Data Model which is used in this implementation can be found on http://www.isotopicmaps.org/sam/sam-model/. ==== License Copyright 2009 Topic Maps Lab, University of Leipzig. Apache License, Version 2.0
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.