I've been following this blog post on how to set up an api-only Rails 5 application. One of the sections talks about creating a subdomain for your api
Rails.application.routes.draw do
constraints subdomain: "api" do
scope module: "api" do
I've been following this blog post on how to set up an api-only Rails 5 application. One of the sections talks about creating a subdomain for your api
Rails.application.routes.draw do
constraints subdomain: "api" do
scope module: "api" do
Inspired by dannyfritz/commit-message-emoji
See also gitmoji.
Commit type | Emoji |
---|---|
Initial commit | 🎉 :tada: |
Version tag | 🔖 :bookmark: |
New feature | ✨ :sparkles: |
Bugfix | 🐛 :bug: |
#!/bin/env ruby | |
# (C) 2015 Thomas R. Koll, <[email protected]> | |
# licensed under WTFPL | |
# | |
# This script generates entries for the ledger format. | |
# Think of it as an envelope generator | |
require 'highline' | |
require 'date' | |
require 'active_support/core_ext/date/calculations' |
In this gist I would like to describe an idea for GraphQL subscriptions. It was inspired by conversations about subscriptions in the GraphQL slack channel and different GH issues, like #89 and #411.
At the moment GraphQL allows 2 types of queries:
query
mutation
Reference implementation also adds the third type: subscription
. It does not have any semantics yet, so here I would like to propose one possible semantics interpretation and the reasoning behind it.
# @author Erik Elmore <[email protected]> | |
# This is getting a little out of hand... :dizzy_face: | |
# For printing trace output for demonstration | |
module Status | |
def status( method_name, args = [], extra = nil ) | |
extra = ' => %s' % extra if extra | |
puts '%s#%s(%s)%s' % [self.class, method_name, args.join(', '), extra] | |
end | |
end |
defmodule Optional do | |
defmacro __using__(_opts) do | |
quote do | |
require unquote(__MODULE__) | |
import unquote(__MODULE__) | |
end | |
end | |
def unit(nil), do: {:err, nil} | |
def unit(value), do: {:ok, value} |
These notes are taken while reading "Liftoff: Launching Agile Teams & Projects".
When projects start, a liftoff generates the momentum team need to overcome the inertia presented by lack of common purpose, unclear communication channels, undefined working relationships, and other areas of ambiguity.
A liftoff also provides the positive force that moves a project toward its destination's successful delivery.
A great proportion of the issues teams wrestle with can be traced back to a lack of clarity and alignment from early days of the project: miscommunications, unexamined assumptions, and misperceptions create an environment in which people make decisions and take actions that unintentionally work at cross-purposes and undermine overall progress.
// Creating Google’s “Material Design” in SCSS | |
// (specifically Material Shadow, uses compass) | |
// see: http://www.google.com/design/spec/layout/layout-principles.html#layout-principles-paper-craft | |
// Demo: http://codepen.io/stoikerty/full/Glwxi/ | |
// Animating Box-Shadow is EXPENSIVE: | |
// http://www.html5rocks.com/en/tutorials/speed/high-performance-animations/#toc- | |
// Moving between z-index-depths is done via opacity & multiple |
# Install Git needed for Git based gems | |
packages: | |
yum: | |
git: [] | |