Lucas Charles theoretick

My Elixir Deployment Wishlist

Foreward

Based on my recent experience of deployment, I've become rather frustrated with the deployment tooling in Elixir. This document is the result of me thinking to myself, "I wish we had x...". This document isn't meant to dishearten anyone who has built tooling for elixir - thank you so much for what you've done. This is meant more as what I personally see as something that would help a lot of Erlang/Elixir newbies like myself to be able to get deploying quickly and efficiently.

1. Release files should be templates

It should be possible to add in custom configuration to the bootstrap scripts. This would allow plugins to be able to add extra steps to the startup / shutdown / upgrade procedure. One way to implement this would be to make all scripts which handle bootstrapping or controlling the machine [.eex][1] templates. This would allow other parts of the release system to inject new functionality where needed.

Firefox bullshit removal

Updated: Just use qutebrowser (and disable javascript). The web is done for.

	# Ticker
	defmodule Ticker do
	use GenServer

	def start_link(%{module: module, function: function, interval: interval} = state)
	when is_atom(module) and is_atom(function) and is_integer(interval) and interval > 0 do
	GenServer.start_link(__MODULE__, state)
	end

	def init(state) do

	using System;
	using System.Collections.Generic;
	using System.Net.Http;
	using System.Net.Http.Headers;

	namespace HttpClientApproach
	{
	internal class Contributor
	{
	public string Login { get; set; }

	require "sequel"

	DB = Sequel.postgres("arel")
	DB.create_table!(:movies) { primary_key :id }

	class Movie < Sequel::Model
	end

	# Asterisk (I agree this one isn't ideal)
	Movie.select{count{}.} # SELECT count() FROM "movies"

	defmodule Life do
	@docmodule """
	This program simulates John Conway's "Game of Life"
	on a small board of size 8x8 cells. The default board executes
	a "glider" that runs from the top left to the bottom right of the board.
	The board does not wrap around to the top/bottom or sides.

	The primary data structure is a list of lists (8x8), which contains
	the board representation. Coords are [row, col]: [0,0] ... [0,7]
	... ...

	daemon off;

	worker_processes 1;

	events { worker_connections 1024; }

	http{

	sendfile on;

Lucas Charles theoretick

My Elixir Deployment Wishlist

Foreward

1. Release files should be templates

Firefox bullshit removal

Quicklook Plugins

Xcode Pluings

	require "active_record"

	ActiveRecord::Base.establish_connection('postgres:///testing')
	ActiveRecord::Migration.verbose = false

	ActiveRecord::Migration.class_eval do
	create_table :played_quizzes, force: true do \|t\|
	t.integer :player_ids, array: true
	t.json :quiz_snapshot
	end

	{
	"auto_match_enabled": false,
	"binary_file_patterns":
	[
	"*.jpg",
	"*.jpeg",
	"*.png",
	"*.gif",
	"*.ttf",
	"*.tga",