This creates a $buildphar as $root/$target/foo.phar
+ one phar per tag as $root/$target/download/$tag/foo.phar
It also dumps the latest git commit hash built in $root/$target/version
This creates a $buildphar as $root/$target/foo.phar
+ one phar per tag as $root/$target/download/$tag/foo.phar
It also dumps the latest git commit hash built in $root/$target/version
# Option defaults | |
OPT="value" | |
# getopts string | |
# This string needs to be updated with the single character options (e.g. -f) | |
opts="fvo:" | |
# Gets the command name without path | |
cmd(){ echo `basename $0`; } |
var color, i; | |
// Notice: octal literals are not allowed in strict mode. | |
function colorize(color, output) { | |
return ['\033[', color, 'm', output, '\033[0m'].join(''); | |
} | |
for (i = 0; i < 100; i += 1) { | |
color = Math.random() > 0.9 ? 91 : 92; // 91 - red, 92 - green | |
process.stdout.write( colorize(color, '●') ); |
# ~/.gitconfig | |
# Add this to your global git configuration file | |
# Change phpstorm to webstorm, if you use that. | |
# Diff and merge tool changes | |
# Run `git difftool <directory/file>...` or `git mergetool <directory/file>...` | |
[merge] | |
tool = phpstorm | |
[diff] | |
tool = phpstorm |
This is one way to pass some data (API tokens, etc.) to your Jekyll templates without putting it in your _config.yml
file (which is likely to be committed in your GitHub repository).
Copy the environment_variables.rb
plugin to your _plugins
folder, and add any environment variable you wish to have available on the site.config
object.
In a Liquid template, that information will be available through the site
object. For example, _layouts/default.html
could contain:
# install bzr and gource | |
# get a branch of Mir's trunk code | |
# create gource video | |
$ sudo apt-get install bzr gource | |
$ bzr branch lp:mir | |
$ cd mir | |
$ gource \ | |
-s .06 \ |
A Dashing widget that checks whether a server is responding to either an http or ping request. It displays either a check or alert depending on the response.
This is a list of issues or discrepencies between the wording or intention of PSR-2 itself and the CodeSniffer PSR-2 ruleset.
Add suggestions in the comments or tweet me (@philsturgeon) if you have more inconsistencies to report.