JoseMPena JoseMPena

Creating bootable Linux USB using Mac

CentOS, Ubuntu, Slackware, etc. Whatever Linux-based OS it is, you can create a bootable USB for it by using a Mac.

1. Prepare the .iso file

Download it, copy it, whatever it takes to prepare that Linux-based OS .iso file

2. Convert the .iso file into a .img.dmg

Capybara Actions

# Anchor
click_link 'Save'

# Button
click_button 'awesome'

# Both above

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

	http://stackoverflow.com/questions/22667401/postgres-json-data-type-rails-query
	http://stackoverflow.com/questions/40702813/query-on-postgres-json-array-field-in-rails

	#payload: [{"kind"=>"person"}]
	Segment.where("payload @> ?", [{kind: "person"}].to_json)

	#data: {"interest"=>["music", "movies", "programming"]}
	Segment.where("data @> ?", {"interest": ["music", "movies", "programming"]}.to_json)
	Segment.where("data #>> '{interest, 1}' = 'movies' ")
	Segment.where("jsonb_array_length(data->'interest') > 1")

	{
	"facebook":{
	"attachment":{
	"type":"template",
	"payload":{
	"template_type":"button",
	"text":"What do you want to do next?",
	"buttons":[
	{
	"type":"web_url",

	# Let's assume you're driving Capybara in both RSpec request specs & Cucumber,
	# for example you're using Cucumber as a design/documentation tool, and RSpec
	# for the more boring integration tests.

	# You don't want to duplicate your click-this-click-that helpers to e.g.
	# log_in(username, password).
	# You may also have model state setup code which can be shared/reused.

	# Where can it go? How can it be loaded? I've been using the following approach:
	#