Get it from the App Store.
In XCode's Preferences > Downloads you can install command line tools.
CREATE OR REPLACE FUNCTION array_pop(a anyarray, element character varying) | |
RETURNS anyarray | |
LANGUAGE plpgsql | |
AS $function$ | |
DECLARE | |
result a%TYPE; | |
BEGIN | |
SELECT ARRAY( | |
SELECT b.e FROM (SELECT unnest(a)) AS b(e) WHERE b.e <> element) INTO result; | |
RETURN result; |
#!/usr/bin/env ruby | |
gem 'activesupport' | |
gem 'pivotal-tracker' | |
require 'active_support/core_ext/string' | |
require 'pivotal_tracker' | |
API_TOKEN = "YOUR_API_TOKEN" | |
PROJECT_ID = "YOUR_PROJECT_ID" |
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure
flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying
# MODEL | |
class Case < ActiveRecord::Base | |
include Eventable | |
has_many :tasks | |
concerning :Assignment do | |
def assign_to(new_owner:, details:) | |
transaction do |
# Installation | |
Put these files in your `.git/hooks` directory and make them executable. | |
# Changelog | |
## 1.2 | |
* Check for RuboCop updates |
jq — https://jqlang.github.io/jq/ — "like sed for JSON data"
There are several options available for installing jq.
I prefer to use Homebrew: brew install jq
In the new year, I plan on archiving the repositories below. Because I plan on only archiving the repositories, any project that depends on any of these projects will continue to work. However, I will no longer be accepting issues or pull requests and will never tag a new release.
The reality of each of the projects listed below is that I've almost completely ignored issues and pull requests for