christopherlai

FROM elixir:1.9.1-alpine as build

ENV MIX_ENV=prod

WORKDIR /build

RUN apk add --no-cache build-base nodejs yarn && \
    mix local.hex --force && \
    mix local.rebar --force

douglascayers

/**
 * Inspired by @MoOx original script: https://gist.github.com/MoOx/93c2853fee760f42d97f
 * Adds file download per @micalevisk https://gist.github.com/MoOx/93c2853fee760f42d97f#gistcomment-2660220
 * 
 * Changes include:
 *  - Get the description from the `title` attribute instead of `aria-label` (doesn't exist anymore)
 *  - Use style.backgroundColor and parse the rgb(...) to hex (rather than regex parsing of 'style' string)
 *  - Downloads labels to a JSON file named after the webpage to know which GitHub repo they came from.
 * 
 * Last tested 2019-July-27:

joepie91

You don't need a blockchain.

If you're reading this, you probably suggested to somebody that a particular technical problem could be solved with a blockchain.

Blockchains aren't a desirable thing; they're defined by having trustless consensus, which necessarily has to involve some form of costly signaling to work; that's what prevents attacks like sybil attacks.

In other words: blockchains must be expensive to operate, to work effectively. This makes it a last-resort solution, when you truly have no other options available for solving your problem; in almost every case you want a cheaper and less complex solution than a blockchain.

In particular, if your usecase is commercial, then you do not need or want trustless consensus. This especially includes usecases like supply chain tracking, ticketing, and so on. The whole *p

fasiha

Well, that was unexpected. In the following, I’m trying to follow Jon Evans’ advice from “The Terrible Technical Interview”.

---

To: recruitment@EmployerABC.com
From: Ahmed Fasih
Subject: Re: Programming Test Invitation

Hi there! Thanks for offering to let me take a HackerRank test for ABC, I appreciate the vote of confidence.

chrismccord

If you want a run-down of the 1.3 changes and the design decisions behidn those changes, check out the LonestarElixir Phoenix 1.3 keynote: https://www.youtube.com/watch?v=tMO28ar0lW8

To use the new phx.new project generator, you can install the archive with the following command:

$ mix archive.install https://github.com/phoenixframework/archives/raw/master/phx_new.ez

Bump your phoenix dep

Phoenix v1.3.0 is a backwards compatible release with v1.2.x. To upgrade your existing 1.2.x project, simply bump your phoenix dependency in mix.exs:

sheharyarn

/**
 * Axios Request Wrapper
 * ---------------------
 *
 * @author  Sheharyar Naseer (@sheharyarn)
 * @license MIT
 *
 */

import axios     from 'axios'

danielberkompas

defmodule MyApp.Scheduler do
  @moduledoc """
  Schedules a Mix task to be run at a given interval in milliseconds.

  ## Options

  - `:task`: The name of the Mix task to run.
  - `:args`: A list of arguments to pass to the Mix task's `run/1` function.
  - `:interval`: The time interval in millisconds to rerun the task.

bitwalker

This is not meant to be comprehensive, a guide, or anything quite that sophisticated, just a couple
notes on what I do at work, in production, and how my environment is set up.

Overview:

- Infrastructure runs on AWS
- We run an internal PaaS based on OpenShift Origin/Kubernetes
- We push code to GitHub, which triggers a webhook, which in turn
  triggers OpenShift to start a build, which fetches the source
  code, and runs the build using the Dockerfile contained in the

cloud8421

defmodule MsTest do
  use ExUnit.Case
  doctest Ms

  @bob %{name: "Bob", job: "developer"}
  @alice %{name: "Alice", job: "musician"}
  @john %{name: "John", job: "musician"}
  @ada %{name: "Ada", job: "developer"}
  @alan %{name: "Alan", job: "developer"}
  @table :users

christhekeele

# For simpler use cases, see the UsesTracker instead:
# https://gist.github.com/christhekeele/e858881d0ca2053295c6e10d8692e6ea


###
# A way to know, at runtime, what modules a module has used at compile time.
# In this case, you include `IndirectUsesTracker` into a module. When that module gets
# used in some other module, it makes that module registerable under a namespace of your choosing.
# When the registerable module is used into a third module, that third module will know at runtime which
# registerables were `use`d in it at compile time, via a function titled after the namespace.