devblog

All those little setup tweaks and installs I tend to do on a shiny new Mac. Wish I’d written this when I first set up my machine... I’ll add to it little by little.

Set finder to default to current folder search

http://apple.stackexchange.com/a/40016

Show keychain access icon in menu bar

http://osxdaily.com/2011/02/10/lock-mac-desktop-via-menu/

git checkout -

...changes to the previous branch.

If your hosting provider won't alter your webroot path, you may be compelled to use Laravel without a public folder. You can achieve this by taking the following steps:

Move all files from public/ up one level to the root (including .htaccess)

Change the bootstrap paths in index.php (see https://gist.github.com/bluefuton/8d2f55c1b7275b97f043/revisions)

Add non-public file restriction to main .htaccess 

<FilesMatch "(artisan|composer.json|composer.lock|phpunit.xml|server.php)$">          deny from all </FilesMatch>

To restrict non-public directory access, add a .htaccess file in all non-public folders (app, bootstrap, packages, vendor) containing:

deny from all

If you're using Apache's VirtualDocumentRoot together with mod_rewrite, and you're seeing an error like:

Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.

Try adding

RewriteBase /

This will handle filenames containing spaces.

Pop this into your .bash_profile:

PROMPT_COMMAND='echo -ne "\033]0; ${PWD}\007"'

Thanks to @tszarzynski.

In your working copy:

tar -cf archive.tar `svn diff -r 542:HEAD --summarize | awk '{print $2}' | grep -vw "."`

We use four spaces to indent our PHP files. If you have some tabs lurking around, you can use expand to replace tabs with spaces across an entire project.

If you call array_filter without a callback function, it'll remove all array elements that evaluate to false (including zeroes).

$numbers = array(0, 1, 2, 0); echo array_filter($numbers);

Produces:

I miss Ruby's shorthand collect method to return an array of single attributes:

animals.collect(&:name)

...so I've created a (less elegant) equivalent for PHP.

class ArrayExtensions { /** * From an array of objects, create a new array containing only * a single attribute of each object * * Similar to array.collect(&:attribute) in Ruby */ public static function collect_by_attribute($attribute, $array_of_objects) { if (!is_array($array_of_objects)) { return array(); } $output = array(); foreach ($array_of_objects as $object) { if (is_object($object) && isset($object->$attribute)) { $output[] = $object->$attribute; } } return $output; } }

Use it like this:

$colours = ArrayExtensions::collect_by_attribute('colour', $animals);

...and you'll get a simple array containing just the attribute you've specified:

array('brown', 'blue', 'green')

Update

If you happen to be using PHP ActiveRecord, they have a function called collect that will accomplish the same thing.

You can't use file_exists because it doesn't search the include path.

fopen has a third argument that will check the include path, though:

Rather than > or >>, use tee.

Redirecting the output of commands run with sudo requires a different approach. For instance consider sudo ls > /root/somefile will not work since it is the shell that tries to write to that file. You can use ls | sudo tee -a /root/somefile to append, or ls | sudo tee /root/somefile to overwrite contents.

Most new code is checked into the trunk.  In general, our developers try to never "break the tree".  Anyone who checks in code which causes the trunk builds to fail will be the recipient of heaping helpings of trash talk and teasing until he gets it fixed.  The trunk should always build, and as much as possible, the resulting build should always work. Most new code is checked into the trunk. The trunk is the place where active development of new features is happening.  The trunk could be described as "basically unstable". In our situation, the stability of the trunk build fluctuates over the months during our development cycle. During the early and middle parts of a development cycle, the trunk is often not very stable at all.  As we approach alpha, beta and final release, things settle down and the trunk gets more and more stable. At the moment of release, a branch gets created.  This branch becomes our maintenance tree for that release.  Our current maintenance branch is called "3.0", since that's the current major version number of our product.  When we need to do a bug fix or patch release, it is done in the maintenance branch.  Each time we do a release out of the maintenance branch (like 3.0.2), we apply a tag. After the maintenance branch is created, the trunk once again becomes "basically unstable".  Developers start adding the risky code changes we didn't want to include in the release.  New feature work begins.  The cycle starts over and repeats itself.