Test if a process is the master in a cluster.
The safe way to handle the `connect` socket event
Execute a listener when a response is about to write headers
smart-buffer is a Buffer wrapper that adds automatic read & write offset tracking, string operations, data insertions, and more.
Execute a callback when a request closes, finishes, or errors
The ultimate javascript content-type utility.
TypeScript definitions for range-parser
Info about your dev environment for debugging purposes
TypeScript definitions for jest-when
A JS implementation of JSONPath with some additional operators
CLS using AsynWrap instead of async-listener - Node >= 4.7.0
Simple, unobtrusive authentication for Node.js.
Drop cursor plugin for ProseMirror
Simplify your schema by combining allOf into the root schema, safely.
Automatic transforms on text input for ProseMirror
request body parsing for co
shim for require.main.filename() that works in as many environments as possible
Serve static files
This package uses ES2015 decorators to simplify JSON schema creation and use
Higher-level content negotiation
Parse HTTP request cookies
A lightweight Promises/A+ and when() implementation, plus other async goodies.
Development-only error handler middleware
TypeScript definitions for undertaker-registry
is_master execute a command when it determine that server is master
A simple class to aquire and check process-id file based locks on a unix filesystem.
A Guilded (http://github.com/midas/guilded/tree/master) component that highlights form fields when they are selected or when they have a validation error.
A puppet-lint extension that warns when you use racist terminology in your code. Starting terms: whitelist, blacklist, master, slave
Deliver all master files managed in a single master snapshot directory into the specified directory while maintaining the hierarchy of the master snapshot directory. If the destination file already exists, back it up first and then deliver the master file. The difference with rsync is that master_delivery creates a symlinks instead of copying the master files. They are symlinks, so you have to keep in mind that you have to keep the master files in the same location, but it also has the advantage that the master file is updated at the same time when you directly make changes to the delivered file. Do you have any experience that the master file is getting old gradually? master_delivery can prevent this. If the master directory is git or svn managed, you can manage revisions of files that are delivered here and there at once with commands like git diff and git commit.
ActiverecordDataImporter is enable to load and import file (format is csv, json) for ActiveRecord's model. For example, when you must use and import master data(ex. game character, enemy, and item stc), it will help you.
Develop on .pre branches, only allow releases from non-.pre clean, up-to-date master. Designed to allow Travis CI to do the push when on a release version, after passing tests.
This is the workflow we use when developing zena. The main idea is that developers work on feature branches on their fork and send an email to the reviewer when work is ready. The reviewer pulls from these branches, checks that all is good and either apply the commits to the gold master or abort. There is a script called 'gold' that helps use this workflow once the remote references are added. Any questions ? Ask zena's mailing list: http://zenadmin.org/en/community ~~
Red Cluster brings together a set of redis servers and allows you to read and write to them as though you were writing to just one. A few of the reasons you might want to consider clustering could be: * Robustness - Having a write master and read slaves * Harnessing the multiple cores you have running while not compromising on the speed of redis * Fault tolerance - When one of the masters goes down a slave in the replica sets gets promoted \ automatically, with no down-time
Mongoid fork with support for Rails 4, for gem development. When releasing a gem, the gem can only depend on other released gems, not on github sources or paths. Mongoid has not yet released a gem supporting Rails 4. This gem is just a packaged version of the mongoid master branch, filling the gap until a release of mongoid with support for Rails 4.
Mongoid fork with support for Rails 4, for gem development. When releasing a gem, the gem can only depend on other released gems, not on github sources or paths. Mongoid has not yet released a gem supporting Rails 4. This gem is just a packaged version of the mongoid master branch, filling the gap until a release of mongoid with support for Rails 4.
This plugin adds a dbdump command which dumps your Rails database out. This master branch supports Rails 3.0 and above, as a gem command. For Rails 2.3, use the rails_2_3 branch from github and install as a plugin. Like rails dbconsole, it takes your database connection details from config/database.yml, and supports mysql, mysql2, postgresql, and sqlite. It takes the same options as rails dbconsole, ie. -p to supply the password to your dump program for mysql and postgresql. (Note that for mysql, this means that the password is visible when other users on the system run 'ps'. Postgresql does not have this problem as it uses an environment variable set in ENV before execing and so not visible in ps.)
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.