andreapavoni

module Slug exposing (..)

import Html exposing (Html, Attribute, beginnerProgram, text, div, input)
import Html.Attributes exposing (..)
import Html.Events exposing (onInput)
import String exposing (toLower)
import Regex exposing (replace, regex)

-- MAIN

andreapavoni

// Pizza Party (#8 from https://pragprog.com/book/bhwb/exercises-for-programmers)

// Write a program to evenly divide pizzas. Prompt for the number of people, the
// number of pizzas, and the number of slices per pizza. Ensure that the number of
// pieces comes out even. Display the number of pieces of pizza each person should
// get. If there are leftovers, show the number of leftover pieces.

// Challenges
// * Revise the program to ensure that inputs are entered as numeric values.
// * Alter the output so it handles pluralization properly, for example:

andreapavoni

defmodule EventPayloadEncoderError do
  @type t :: %__MODULE__{message: String.t(), value: any}

  defexception message: nil, value: nil

  def message(%{message: nil, value: value}) do
    "unable to serialize value: #{inspect(value)}"
  end

  def message(%{message: message}) do

andreapavoni

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.

Conceptual Model

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.

andreapavoni

# ...

release :my_app do
  # ...

  set(
    applications: [
      :runtime_tools,
      my_app: :permanent
    ]

andreapavoni

Prelude

I. Preface and Motivation

This guide was written because I don't particularly enjoy deploying Phoenix (or Elixir for that matter) applications. It's not easy. Primarily, I don't have a lot of money to spend on a nice, fancy VPS so compiling my Phoenix apps on my VPS often isn't an option. For that, we have Distillery releases. However, that requires me to either have a separate server for staging to use as a build server, or to keep a particular version of Erlang installed on my VPS, neither of which sound like great options to me and they all have the possibilities of version mismatches with ERTS. In addition to all this, theres a whole lot of configuration which needs to be done to setup a Phoenix app for deployment, and it's hard to remember.

For that reason, I wanted to use Docker so that all of my deployments would be automated and reproducable. In addition, Docker would allow me to have reproducable builds for my releases. I could build my releases on any machine that I wanted in a contai

andreapavoni

<tags-input>
  <%= hidden_input form, :tags, value: [] , class: "input" %>
</tags-input>

andreapavoni

Ever found yourself writing code like this?

case Mix.env() do
  :prod -> do_something1()
  :dev  -> do_something2()
  :test -> do_something3()
end

andreapavoni

# MYAPP/.deliver/config

APP="<APP NAME>"
MAIN_HOST="<BUILD & PRODUCTION HOST>"
MAIN_USER="<MAIN USER FOR BUILD AND DEPLOY>"

BUILD_HOST="${MAIN_HOST}"
BUILD_USER="${MAIN_USER}"
BUILD_AT="/tmp/edeliver/${APP}/builds"

andreapavoni

module Geometry do
  @moduledoc """
  Calculates area of different shapes
  """
  
  @doc """
  Some other comment
  """
  def area({:rectangle, width, height}) do:  width * height
  def area({:square, side}) do:  side * side