aergonaut

How to use

cd /etc/init.d
curl $RAW_GIST_URL -o minecraft
chmod a+x minecraft

Make sure to edit the script and change the configuration variables at the top to match your system.

hamin

require "./points"

p1 = RustPoint::make_point(10, 10) #  => #<Fiddle::Pointer:0x007f8231e56510 ptr=0x0000010b824000 size=0 free=0x00000000000000> 
p2 = RustPoint::make_point(20, 20) #  => #<Fiddle::Pointer:0x007f8231f20970 ptr=0x0000010b824010 size=0 free=0x00000000000000> 

RustPoint::get_distance(p1, p2) # => 14.142135623730951 

jpemberthy

config = Rails::Configuration.new
database = config.database_configuration[RAILS_ENV]["database"]
username = config.database_configuration[RAILS_ENV]["username"]
password = config.database_configuration[RAILS_ENV]["password"]

namespace :db do
  
  #rake db:dump
  desc "dumps the database to a sql file"
  task :dump => :environment do

wycats

A small sampling of external projects initially built for Ember use but designed to be used standalone:

• Handlebars - templating engine
• simple-html-tokenizer - an HTML5 tokenizer
• HTMLBars - alternate HTML-aware Handlebars backend
• morph - text-node placeholders for data binding systems
• RSVP - fast, lightweight promise library
• route-recognizer - just the recognition part of a router
• router.js - hierarchical states and transition-based router
• dag-map - graph library

edjames

namespace :db do
  namespace :data do
    desc "Dump data into sql script file: filename=[target filename]"
    task :dump => 'environment' do
      environment = (ENV.include?("RAILS_ENV")) ? (ENV["RAILS_ENV"]) : 'development'
      ENV["RAILS_ENV"] = RAILS_ENV = environment

      database = get_database(environment)
      user = database
      password = ENV['PASSWORD']

rosskevin

// @flow

declare module 'react-relay' {
  declare export type RecordState = 'EXISTENT' | 'NONEXISTENT' | 'UNKNOWN';

  declare export type onCompleted = (response: ?Object, errors: ?Array<PayloadError>) => void
  declare export type onError = (error: Error) => void

  declare export type CommitOptions = {
    onCompleted: onCompleted,

rattrayalex

var ChatAppDispatcher = require('../dispatcher/ChatAppDispatcher');
var ChatConstants = require('../constants/ChatConstants');
var ChatMessageUtils = require('../utils/ChatMessageUtils');
var EventEmitter = require('events').EventEmitter;
var ThreadStore = require('../stores/ThreadStore');
var merge = require('react/lib/merge');

var ActionTypes = ChatConstants.ActionTypes;
var CHANGE_EVENT = 'change';

burke

# typed: true
# frozen_string_literal: true
require('dev')
require('fileutils')

module Dev
  module Helpers
    class APFSVolume
      extend(T::Sig)

atmos

@holman got a request about our deployment system, heaven

I know it's not a high priority, but has there been any activity on open-sourcing the core Heaven gem?

There is. I've been working on extracting the non-GitHub specific parts into two gems. This first is a CLI portion called hades. The second is an HTTP API portion called heaven.

When you open source something previously used as in internal tool like Heaven, Hubot, Boxen, etc., how do you manage and hook in the parts that need to stay internal?

Normally I focus around four questions:

Vazkii

/**
 * This class was created by <Vazkii>. It's distributed as
 * part of the Psi Mod. Get the Source Code in github:
 * https://github.com/Vazkii/Psi
 * 
 * Psi is Open Source and distributed under the
 * CC-BY-NC-SA 3.0 License: https://creativecommons.org/licenses/by-nc-sa/3.0/deed.en_GB
 * 
 * File Created @ [11/01/2016, 22:00:30 (GMT)]
 */