mohsen1

var https = require('https');
var fs = require('fs');
var url = 'https://raw.githubusercontent.com/dconnolly/chromecast-backgrounds/master/backgrounds.json';

Array.prototype.getLast = function() {
  return this[this.length - 1];
};

function logFail(err){
  console.log('Failed!');

JeffreyWay

Laravel 4 Thoughts/Questions/Etc.

This is just a random list of notes, as I dig into Laravel 4. If you have any feedback/solutions, please leave a comment. I'll be compiling everything for an article on Nettuts+, when the framework is officially in Beta. This will be updated over the course of the week.

• Running composer dump-autoload after every new controller is a pain. Can this not be automated through artisan controller:make ControllerName?

• Seems that some of the View HTML helpers are missing. No HTML::script().

• Route::resource('tasks', 'TasksController') doesn't seem to create named routes. This is a big deal, if not. What's the solution?

nateware

1. Create the appropriate VPC that your application is going to live in. Create subnets for each availability zone you want to use.

2. Create VPC security group(s) for your auto-scaling instances. For example, if you're going to auto-scale web servers, create a "web" VPC security group.

3. Go into AWS console and create an ELB. Easy wizard. Select HTTP and (if needed) HTTPS. Make sure it's associated with the VPC you created in step 1.

4. Create an auto-scaling launch configuration from the CLI. The launch configuration has the AMI, size, and security group from step #2. The security group must be by ID not name ("sg-12345"):

      as-create-launch-config web --image-id ami-2e31bf1e --instance-type m1.medium \
   

-g sg-7619041a --key root

latentflip

#depends on underscore

_.isConstructor = (thing) ->
  if thing.name && thing.name[0].toUpperCase() == thing.name[0]
    true
  else
    false

class Instrumentor
  constructor: (namespace) ->

mipearson

# adapted from https://gist.github.com/nruth/484787
module CookieStepHelper
  def save_selenium_cookie_jar domain
    cookies = Capybara.current_session.driver.browser.manage.all_cookies.select do |cookie|
      domain.end_with? cookie[:domain]
    end
    File.binwrite(cookie_jar_path(domain), Marshal.dump(cookies))
  end

  def load_selenium_cookie_jar domain, fake_domain_url=nil

pat

I've written this code to test what happens once a Stripe card token has been passed through to the server. This code does not do any browser testing (because JS-friendly headless testing is painful at best, and impossible if you want VCR in the mix). VCR is being used here to capture interactions with a test Stripe account, to ensure the tests are fast on future runs. That said, it's structured so that nothing is expected to be present in the Stripe account. If you delete all the stored VCR cassettes, the specs will safely re-record them.

Instead of using VCR.use_cassette directly, instead you use stripe_cassette in your specs, passing in the current spec example object. This will automatically generate a cassette name based on the spec's file name and the example's description (limitations of this are noted in the code comments). Within the cassette's recording block, Stripe data is cleared out before yielding back to the spec, with a context object. The context object provides access to helper methods

moriyoshi

Index: sapi/cli/config.w32
===================================================================
--- sapi/cli/config.w32	(revision 308839)
+++ sapi/cli/config.w32	(working copy)
@@ -6,7 +6,8 @@
 ARG_ENABLE('cli-win32', 'Build console-less CLI version of PHP', 'no');
 
 if (PHP_CLI == "yes") {
-	SAPI('cli', 'php_cli.c', 'php.exe');
+	SAPI('cli', 'php_cli.c php_http_parser.c php_cli_server.c', 'php.exe');

msroot

require "delegate"  
  
class CollectionProxy  
  def products
    @products                  ||= HasManyAssociation.new([])  
    @products.associated_class ||= Product  
    @products
  end  
end