sadams

function use_crawlera(splash)
    local password = ''
    local host = 'proxy.zyte.com'
    local port = 8011
    local session_header = 'X-Crawlera-Session'
    local session_id = 'create'

    splash:on_request(function (request)
        request:set_proxy(host, port, 'PUT_CRAWLERA_AUTH_HERE', password)
        request:set_header('X-Crawlera-Profile', 'desktop')

sadams

Cars Web Dev Test

Cars API

Please create a new git repo and follow the instructions below.

Once you have finished, please email us the URL to your repo.

Please make commits as you go (> 1 and < 100) and provide instructions to run the application.

sadams

<?php
/**
 * A very edge case in PHP 5.4 regarding passing objects by reference. 
 * It seems to be a compound effect of using reflection to set an inherited method as 'available', 
 * AND that method taking an explicitly referential argument (&argument sig) 
 * AND then invoking it with func_get_args() as opposed to constructing the array of args manually.
 * 
 * No idea why these things all cause this behaviour or if they should.
 * 
 * Important to note that this effect isn't present in PHP 5.5.

sadams

OSX Mountain Lion LAMP pear etc Install

If you are really lazy

Install your existing keychains on new mac (there are some files you can just copy, but i can't remember which so maybe give this a go): http://osxdaily.com/2012/07/05/copy-keychain-login-passwords-between-macs/

SSH

• turn on Remote Login from Sharing in System Preferences
• Run ssh localhost, the ctrl+c to cancel (cheap way to create the .ssh directory in home dir)
• Copy private key into .ssh dir and call it id_rsa (make sure perms are 600 or similar)

sadams

releasing with git flow

git checkout develop
git pull

start the release branch off develop (assuming we have a current version of '1.0.0-SNAPSHOT');

git flow release start 1.0.0

in the code, update your version to '1.0.0', and commit your changes:

sadams

understanding first/third party cookie behaviour

scenario 1

1. set cookie from foo.example.com with no domain
2. is it readable by foo.example.com?
3. is it readable by bar.example.com?
4. is it overwritable by bar.example.com?

scenario 2

sadams

notes on sudoers

to view/edit:

/etc/sudoers

or

visudo