jpinnix

[T]he difference between a bad programmer and a 
good one is whether he considers his code or his 
data structures more important. Bad programmers 
worry about the code. Good programmers worry about 
data structures and their relationships. 
-- Linus Torvalds
~~~
Clarity and brevity sometimes are at odds. 
When they are, I choose clarity. 
-- Jacob Kaplan-Moss

jpinnix

Oh my zsh.

Install with curl

sh -c "$(curl -fsSL https://raw.githubusercontent.com/robbyrussell/oh-my-zsh/master/tools/install.sh)"

Enabling Plugins (zsh-autosuggestions & zsh-syntax-highlighting)

• Download zsh-autosuggestions by

jpinnix

#!/usr/bin/env python
#
# Convert .itermcolors files to hex colors for html

import sys
import xml.etree.ElementTree as ET

def rgb_to_hex(rgb):
	return '#%02x%02x%02x' % rgb

jpinnix

#!/usr/bin/env python3
#
# Convert .itermcolors files to kitty terminal color settings.
# Modded from https://gist.github.com/MSylvia/4e90860743f1a4de187d
# Might need to adjust dicts[i][NUMBER].text per your file.

import sys
import xml.etree.ElementTree as ET

def rgb_to_hex(rgb):

jpinnix

@media screen and (max-width: 991px) {
  /* Your responsive CSS */
}
@media screen and (max-width: 767px) {
  /* Your responsive CSS */
}
@media screen and (max-width: 479px) {
  /* Your responsive CSS */
}

jpinnix

# This is the target module which will be overwritten after dynamic compilation
# You'll be using this to read configuration in your code. For instance, if you
# have a configuration key called `:redis_timeout`, you could read it using
# `MM.Config.get(:redis_timeout)`
defmodule MM.Config do
  # we use a default implementation which raises an error when our code tries
  # to read configuration before it is compiled.
  def get(_key), do: raise("Config has not been compiled yet!")
end

jpinnix

defmodule MdToolbox.Api.SoapMethod do
  alias __MODULE__
  alias MdToolbox.Api.Request

  @doc "Builds the request from params"
  @callback build_request(params :: list()) :: map()

  @doc "Parses the request's response into data"
  @callback parse_response(request :: Request.t()) :: Request.t()

jpinnix

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

jpinnix

--==============================
-- Send Keynote Text to Desktop Markdown File
-- Writted By: Richard Dooling https://github.com/RichardDooling/
-- Based on 
-- Send Keynote Presenter Notes to Evernote
-- Version 1.0.1
-- Written By: Ben Waldie <[email protected]>
-- http://www.automatedworkflows.com

-- Version 1.0.0 - Initial release

jpinnix

Server Price Breakdown: DigitalOcean, Amazon AWS LightSail, Vultr, Linode, OVH, Hetzner, Scaleway/Online.net:

Sorted (Descending): Network, Cores, RAM, Storage, Transfer

$5/mo

Provider	Type	RAM	Cores	Storage	Transfer	Network	Price