ChristianAlexander

Podcast Transcription

Mix.install([
  {:req, "~> 0.4.14"},
  {:fast_rss, "~> 0.5.0"},
  {:bumblebee, "~> 0.5.3"},
  {:exla, "~> 0.7.1"},
  {:kino, "~> 0.12.3"}
])

caspg

defmodule TravelerWeb.SearchbarLive do
  use TravelerWeb, :live_view

  alias Phoenix.LiveView.JS
  alias Traveler.Places

  def mount(_params, _session, socket) do
    socket = assign(socket, places: [])
    {:ok, socket, layout: false}
  end

teamon

defmodule SupportChat do
  import Phoenix.Component
  alias Phoenix.LiveView.JS

  @doc """
  Chat bubble at the bottom right corner.
  """
  def bubble(assigns) do
    ~H"""
    <div>

micahboyd

defmodule ServerProcess do

  def start(callback_module) do
    spawn(fn ->
      initial_state = callback_module.init
      loop(callback_module, initial_state)
    end)
  end

  def call(server_pid, request) do

jswny

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

pbochenski

class MainViewModel(app: Application) : AndroidViewModel(app) {    
  private val postRepo = getApplication<App>().postRepo  
  private val LOAD_ITEM_COUNT = 15    
  
  fun getPosts(): LiveData<List<Post>> {        
    return postRepo.posts.map {                     
      it.map { Post(it.id, it.title, it.url) } 
    }    
  }    
  

brienw

Deploying Elixir and Phoenix applications using Docker and Exrm

Goal

By the end of this quick guide, you will know how to compile a Phoenix app release using Exrm and run it inside a Docker container. I've found only a couple of articles that discuss getting an Elixir app up and running inside a Docker container, and even those only touched on some parts of the process. The idea is that this guide will give you a full end-to-end example of how to get all the pieces and parts working together so that you are able to deploy your Phoenix application inside a Docker container.

Assumptions

1. You already have a working Elixir environment with the Phoenix Framework installed
2. You have at least basic working knowledge of Docker, and have installed the Docker tools onto your local environment

kf0jvt

defmodule Mailgun do
  @doc """
  Sends a basic message to an address. Expects a mailgun domain environment
  variable (MAILGUN_DOMIAN) and a mailgun api key environment variable
  (MAILGUN_API_KEY).
  """
  @spec mail(String.t) :: String.t
  def mail(toAddress) do
    url = "https://api.mailgun.net/v3/#{System.get_env("MAILGUN_DOMAIN")}/messages"
    headers = ["User-Agent": "Elixir",

col

Configure Elixir app on Travis CI

Setup Build

1. Create .travis.yml file in the base dir
2. Enter the following content:

language: elixir
elixir:
 - 1.2

vysakh0

defmodule Parser do
  require Record

  Record.defrecord :xmlElement, Record.extract(:xmlElement, from_lib: "xmerl/include/xmerl.hrl")
  Record.defrecord :xmlText,    Record.extract(:xmlText, from_lib: "xmerl/include/xmerl.hrl")
  Record.defrecord :xmlAttribute,    Record.extract(:xmlAttribute, from_lib: "xmerl/include/xmerl.hrl")

  def run(xml) do
    run(xml, '//response')
  end