Index: /main/waeup-ansible/README.rst
===================================================================
--- /main/waeup-ansible/README.rst	(revision 13838)
+++ /main/waeup-ansible/README.rst	(revision 13839)
@@ -91,2 +91,31 @@
   https://docs.ansible.com/ansible/playbooks_best_practices.html#directory-layout
 
+
+Bootstrapping - Freshmechs
+--------------------------
+
+We call those nachines "freshmech" that are freshly delivered from the
+hosting provider or that were freshly provisioned by `vagrant` (see
+above).
+
+These machines are expected to have only a single root account and
+normally a (security-wise) poor SSH configuration.
+
+Bootstrapping these machines means we secure SSH, restart the SSH
+daemon and then add important accounts: "uli", "henrik", "ansible".
+
+Any host you want to "bootstrap" must be entered in a local hosts
+file, normally ``hosts-virtual``, with a line like this:
+
+  [yet-untouched]
+  vh5.sample.org ansible_host=192.168.36.10 ansible_user=root
+
+in the "yet-untouched" section.
+
+Afterwards try:
+
+  $ ansible-playbook -i hosts-virtual --ask-pass bootstrap.yml
+
+The ``ask-pass`` parameter is needed to enter the password given by
+the provider on the commandline. For the local `vagrant` machines this
+will be `vagrant`.
Index: /main/waeup-ansible/bootstrap.yml
===================================================================
--- /main/waeup-ansible/bootstrap.yml	(revision 13839)
+++ /main/waeup-ansible/bootstrap.yml	(revision 13839)
@@ -0,0 +1,18 @@
+---
+# This ansible-playbook prepares fresh-from-hetzner
+# servers for work with ansible.
+#
+# What it does:
+#   secures sshd (according to bettercrypto.org)
+#   adds accounts uli/henrik/deploy
+#   disables root access
+#
+# This playbook should be executed as first thing
+# after getting your hands over new hardware
+#
+# It will normally be run with ``ask-pass``
+#
+- hosts: yet-untouched
+  tasks:
+    - name: "Start"
+      command: echo "Hello world."
