cowboy

This is now an actual repo:

https://github.com/cowboy/jquery-tiny-pubsub

msolomon

                new_user_session GET    /users/sign_in(.:format)                    {:action=>"new", :controller=>"devise/sessions"}
                    user_session POST   /users/sign_in(.:format)                    {:action=>"create", :controller=>"devise/sessions"}
            destroy_user_session DELETE /users/sign_out(.:format)                   {:action=>"destroy", :controller=>"devise/sessions"}
                   user_password POST   /users/password(.:format)                   {:action=>"create", :controller=>"devise/passwords"}
               new_user_password GET    /users/password/new(.:format)               {:action=>"new", :controller=>"devise/passwords"}
              edit_user_password GET    /users/password/edit(.:format)              {:action=>"edit", :controller=>"devise/passwords"}
                                 PUT    /users/password(.:format)                   {:action=>"update", :controller=>"devise/passwords"}
        cancel_user_registration GET    /users/cancel(.:format)            

cayuu

var r = R.player, oVol = r.volume(), tf = r._onTrackFinished, ar = r._onAudioReady, n = r._next;

r._onTrackFinished = function() {
  return .001 !== r.volume() && (oVol = r.volume()), r.volume(.001), tf.apply(this, arguments);
};

r._onAudioReady = function() {
  return r.playingAd() || r.volume(oVol), ar.apply(this, arguments);
};

tracker1

Directory structure for JavaScript/Node Projects

While the following structure is not an absolute requirement or enforced by the tools, it is a recommendation based on what the JavaScript and in particular Node community at large have been following by convention.

Beyond a suggested structure, no tooling recommendations, or sub-module structure is outlined here.

Directories

• lib/ is intended for code that can run as-is
• src/ is intended for code that needs to be manipulated before it can be used

isaacs

# Hello, and welcome to makefile basics.
#
# You will learn why `make` is so great, and why, despite its "weird" syntax,
# it is actually a highly expressive, efficient, and powerful way to build
# programs.
#
# Once you're done here, go to
# http://www.gnu.org/software/make/manual/make.html
# to learn SOOOO much more.

jpillora

package main

import (
	"log"
	"net/smtp"
)

func main() {
	send("hello there")
}

reggi

Glob Up and Running

To test a glob pattern go over to globtester and play around with creating your own file structure online, it's super easy to get started that way.

If you want to test out a glob pattern in the terminal use echo followed by the pattern, for instance.

echo **/*.js

frnhr

####
#### pyenv-virtualenv bash prompt customization
####


# pyenv
eval "$(pyenv init -)"

# pyenv-virtualenv:

zkat

#!/usr/bin/env node

console.log('yay gist')

marwei

Kafka 0.11.0.0 (Confluent 3.3.0) added support to manipulate offsets for a consumer group via cli kafka-consumer-groups command.

1. List the topics to which the group is subscribed

kafka-consumer-groups --bootstrap-server <kafkahost:port> --group <group_id> --describe

Note the values under "CURRENT-OFFSET" and "LOG-END-OFFSET". "CURRENT-OFFSET" is the offset where this consumer group is currently at in each of the partitions.

2. Reset the consumer offset for a topic (preview)