Skip to content

Instantly share code, notes, and snippets.

Rubén Caro rubencaro

Block or report user

Report or block rubencaro

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
@alanpeabody
alanpeabody / my_app.ex
Last active Jul 31, 2019
Websockets in Elixir with Cowboy and Plug
View my_app.ex
defmodule MyApp do
use Application
def start(_type, _args) do
import Supervisor.Spec, warn: false
children = [
Plug.Adapters.Cowboy.child_spec(:http, MyApp.Router, [], [
dispatch: dispatch
])
@rob-brown
rob-brown / ElixirConf2014.md
Last active Sep 16, 2017
Notes from ElixirConf 2014
View ElixirConf2014.md

ElixirConf 2014

Dave Thomas—Opening Keynote

Twitter | Slides

Think different(ly)

Get out of your rut and learn new ways to think.

@datagrok
datagrok / git-branch-simplify.md
Last active Aug 11, 2019
How to simplify the graph produced by git log --graph
View git-branch-simplify.md

Ideas for improvements to git log --graph

I will maybe someday get around to dusting off my C and making these changes myself unless someone else does it first.

Make the graph for --topo-order less wiggly

Imagine a long-running development branch periodically merges from master. The git log --graph --all --topo-order is not as simple as it could be, as of git version 1.7.10.4.

It doesn't seem like a big deal in this example, but when you're trying to follow the history trails in ASCII and you've got several different branches displayed at once, it gets difficult quickly.

You can’t perform that action at this time.