I hereby claim:
- I am jpinnix on github.
- I am jpinnix (https://keybase.io/jpinnix) on keybase.
- I have a public key ASDPw031JHh1g-xUF2MOinTs89eie086s-PdtV-3cEx6zgo
To claim this, I am signing this object:
| /** | |
| * Using Operator Mono in Atom | |
| * | |
| * 1. Open up Atom Preferences. | |
| * 2. Click the “Open Config Folder” button. | |
| * 3. In the new window’s tree view on the left you should see a file called “styles.less”. Open that up. | |
| * 4. Copy and paste the CSS below into that file. As long as you have Operator Mono SSm installed you should be golden! | |
| * 5. Tweak away. | |
| * | |
| * Theme from the screenshot (http://cdn.typography.com/assets/images/blog/operator_ide2.png): |
| #!/usr/bin/env python | |
| """ | |
| This script is designed to generate a simple HTML file with _all_ of your | |
| Pinboard.in bookmarks. | |
| You should edit the `username`, `password`, `bookmark_filename`, and `tag` | |
| variables. | |
| Requirements: |
I hereby claim:
To claim this, I am signing this object:
| @SayersMark | |
| 9 tweets - 12 Mar 2018 | |
| SayersMark/status/973321200179953665 | |
| Much of Lessie Newbigin’s work was to convince the Church in the West that they no longer lived in the context of Christendom, but rather in a pluralist society. In which no particular belief was held up above others, and in which all ideologies were subject to critique. | |
| Yet a cursory glance across our news & social media, show us a reality which no longer seems like a society where all views, ideologies & beliefs are treated the same. A singular route to justice, and reading of the worlds ills is advocated in a way that assumes its supremacy. | |
| ‘Diversity’ & ‘inclusion’ are invoked, but increasingly inclusion into ‘polite society’ is only achieved by those who acquiesce to the one preferred stream of Western thought which is beyond critique. Thus it seems that we have moved away from pluralism to a single ideology. |
| --============================== | |
| -- 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 <ben@automatedworkflows.com> | |
| -- http://www.automatedworkflows.com | |
| -- Version 1.0.0 - Initial release |
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
| 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() |
| Fitter, happier | |
| More productive | |
| Comfortable | |
| Not drinking too much | |
| Regular exercise at the gym, three days a week | |
| Getting on better with your associate employee contemporaries | |
| At ease | |
| Eating well, no more microwave dinners and saturated fats | |
| A patient, better driver | |
| A safer car, baby smiling in back seat |
| # 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 |