beddari

#!/bin/bash
# Script for placing sudoers.d files with syntax-checking

if [ -z "$1" ]; then
  # Making a temporary file to contain the sudoers-changes to be pre-checked
  TMP=$(mktemp)
  cat > $TMP <<EOF
Cmnd_Alias VAGRANT_EXPORTS_ADD = /bin/su root -c echo '*' >> /etc/exports
Cmnd_Alias VAGRANT_NFSD = /etc/init.d/nfs-kernel-server restart
Cmnd_Alias VAGRANT_EXPORTS_REMOVE = /bin/sed -e /*/ d -ibak /etc/exports

gregoryyoung

Greg's Stop Loss Kata

Testing is very hard when time is involved ...

A trailing stop loss is a term used in financial trading. For a very in depth explanation you can read here http://www.investopedia.com/articles/trading/03/080603.asp and http://en.wikipedia.org/wiki/Order_(exchange)#Stop_orders

However we do not need a huge amount of background in order to do the kata as we are going to limit the problem a bit.

The general idea is that when you buy into a stock at a price say $10. You want it to automatically get sold if the stock goes below $9 (-$1). If we use the term "trailing" that means that id the price goes up to $11 then the sell point becomes $10.

nikcub

In August 2007 a hacker found a way to expose the PHP source code on facebook.com. He retrieved two files and then emailed them to me, and I wrote about the issue:

http://techcrunch.com/2007/08/11/facebook-source-code-leaked/

It became a big deal:

http://www.techmeme.com/070812/p1#a070812p1

The two files are index.php (the homepage) and search.php (the search page)

briandoll

To toast:

• Make sure you have ImageMagick installed (brew install imagemagick)
• Change line 7 of toast.rb to the repository name you're working with
• toast!

$ bundle install
$ ./get_token [user] [pass]
$ export GHUSER=[myuser]

callado4

Making behat use phantomjs for the tests

If you want to run it on phantomjs (a headless browser) you can add this profile to your behat.yml and you need phantomjs >= 1.8.0

phantomjs:
    extensions:
        Behat\MinkExtension\Extension:
            base_url: http://dev.local
            goutte: ~
            selenium2:
 wd_host: "http://localhost:8643/wd/hub" 

philsturgeon

Never Expose DB Results Directly

1. If you rename a field, then your users are fucked. Convert with a hardcoded array structure.
2. Most DB drivers [for PHP] will show integers as numeric strings and false as "0", so you want to typecast them.
3. Unless you're using an ORM with "hidden" functionality, people will see passwords, salts and all sorts of fancy codes. If you add one and forget to put it in your $hidden array then OOPS!

Use the URI sparingly, and correctly

1. Use the query string for paired params instead of /users/id/5/active/true. Your API does not need to be SEO optimised.
2. ?format=xml is stupid, use an Accept: application/xml header. I added this to the CodeIgniter Rest Server once for lazy people, and now people think it's a thing. It's not.

seiffert

<?php

namespace Sensio\Bridge\Phpmig;

use Symfony\Component\DependencyInjection\ContainerInterface;

/**
 * The ContainerAdapter allows the Symfony DIC to be used with phpmig. Phpmig is the tool that's used for executing
 * migrations on the application and expects a service container that implements \ArrayAccess. This is achieved by
 * wrapping Symfony's DIC with an adapter that implements \ArrayAccess and proxies to the DIC.

seiffert

<?php

use \Phpmig\Adapter;
use Sensio\Bridge\Phpmig\ContainerAdapter;

require_once __DIR__ . '/autoload.php';
require_once __DIR__ . '/AppKernel.php';

$kernel = new AppKernel('dev', true);
$kernel->boot();

krakjoe

Multi-Threading in PHP with pthreads

A Brief Introduction to Multi-Threading in PHP

• Foreword
• Execution
• Sharing
• Synchronization
• Pitfalls

codeliner

<?php
/**
 * This file is an example gist to show the interaction between an ArticleContext and a LikeContext
 *
 * @example:
 *
 * We have to bounded contexts: ArticleContext and LikeContext and show the simplified process of following use case:
 *
 * In order to create a valid article Like, I should validate the article ID given to the LikeContext.
 *