Add complete tutorial

Author: bricef

README.md

@@ -0,0 +1,25 @@
+# For Github
+
+Go to the _Settings_ tab for your repository. 
+
+![](../resources/github-key-settings.png?raw=true)
+
+Add your key and make sure you toggle write access.
+
+![](../resources/add-key-to-github.png?raw=true)
+
+You're done :)
+
+# For Bitbucket
+
+For Bitbucket, you'll need to add the key to your profile instead of a repository for it to have write access. You can do this from your profile, a link for which you'll find at the bottom left of your screen when logged in:
+
+![](../resources/bitbucket-profile.png?raw=true)
+
+Then, add a new key to your profile:
+
+![](../resources/bitbucket-add-key.png?raw=true)
+
+![](../resources/bitbucket-key.png?raw=true)
+
+

docs/adding-write-keys.md

@@ -0,0 +1,17 @@
+---
+apiVersion: apps/v1beta1 # for versions before 1.6.0 use extensions/v1beta1
+kind: Deployment
+metadata:
+  name: podinfo
+spec:
+  replicas: 1
+  template:
+    metadata:
+      labels:
+        app: podinfo
+    spec:
+      containers:
+      - name: podinfo
+        image: quay.io/stefanprodan/podinfo:1.0.0
+        ports:
+        - containerPort: 3000

docs/digitalocean-install.md

@@ -0,0 +1,37 @@
+---
+# The service account, cluster roles, and cluster role binding are
+# only needed for Kubernetes with role-based access control (RBAC).
+apiVersion: v1
+kind: ServiceAccount
+metadata:
+  labels:
+    name: flux
+  name: flux
+---
+apiVersion: rbac.authorization.k8s.io/v1beta1
+kind: ClusterRole
+metadata:
+  labels:
+    name: flux
+  name: flux
+rules:
+  - apiGroups: ['*']
+    resources: ['*']
+    verbs: ['*']
+  - nonResourceURLs: ['*']
+    verbs: ['*']
+---
+apiVersion: rbac.authorization.k8s.io/v1beta1
+kind: ClusterRoleBinding
+metadata:
+  labels:
+    name: flux
+  name: flux
+roleRef:
+  apiGroup: rbac.authorization.k8s.io
+  kind: ClusterRole
+  name: flux
+subjects:
+  - kind: ServiceAccount
+    name: flux
+    namespace: default