Create a file called /media/state/units/docker-local.service
that has the following contents:
[Unit]
Description=docker local
[Service]
PermissionsStartOnly=true
{-# LANGUAGE OverloadedStrings #-} | |
{-# LANGUAGE DeriveDataTypeable #-} | |
import Data.Aeson | |
import qualified Data.ByteString.Char8 as BS | |
import qualified Data.ByteString.Lazy.Char8 as BSL | |
import Data.ByteString.Lazy (toChunks) | |
import Data.List | |
import Data.Maybe | |
import Data.Typeable (Typeable) |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
Inspiration: Dies Commit Style Guide*
I often quote Dies in sections below.
NOTE - Dies took their style guide from CoreOS who took it from Angular. Will be updating with proper attribution soon.
Red Hat has fully adopted the CoreOS vision of running applications by extending Kubernetes (rather than building on top
using existing primitives). Operators use "provided APIs" (CRDs/apiservers) to give users a way to declaratively manage their
apps. Now you can interact with your services and have the same experience as using the aws
or gcloud
command-line tool,
because everything lives in the Kubernetes API. You have extended Kubernetes. The Operator Lifecycle Manager (OLM) is a comprehensive framework for resolving, installing, and upgrading these extensions in the same declarative way.
The OpenShift Console is a frontend for the Kubernetes API. Each list/detail view has an equivalent kubectl get
(uses the
raw REST endpoints). Naturally, the UI provides a lot of advantages over CLI: aggragating resources into a single view,
hyperlinks to related views, cluster-aware autocompletion for YAML edi