I found you can not run the cp.push commands until after enabling the feature in the conf, so I wanted to update the docs so others who try these commands wont bump into the same issue I had.

doc/topics/tutorials/minionfs.rst

@@ -1,13 +1,27 @@
 .. _tutorial-minionfs:
 
 ============================
-MinionFS Backend Walkthrough
+Propagating Files Walkthrough
 ============================
 
 .. versionadded:: 2014.1.0
 
 Sometimes, you might need to propagate files that are generated on a minion.
-Salt already has a feature to send files from a minion to the master:
+Salt already has a feature to send files from a minion to the master.
+
+Enabling Feature
+====================
+
+To use the propagate feature one configuration change is required on the
+master. The :conf_master:`file_recv` option needs to be set to true.
+
+.. code-block:: yaml
+
+    file_recv: True
+
+These changes require a restart of the master, then new requests for the
+``salt://minion-id/`` protocol will send files that are pushed by ``cp.push``
+from ``minion-id`` to the master.
 
 .. code-block:: bash
 
@@ -24,6 +38,10 @@ This command will store the file, including its full path, under
     <salt.modules.cp.push>`. To get up to speed, check out the
     :doc:`walkthrough </topics/tutorials/walkthrough>`.
 
+============================
+MinionFS Backend Walkthrough
+============================
+
 Since it is not a good idea to expose the whole :conf_master:`cachedir`, MinionFS
 should be used to send these files to other minions.
 
@@ -136,4 +154,4 @@ Or we can use a more elegant and salty way to add an SSH key:
 
 
 
-.. [*] Yes, that was the actual key on my server, but the server is already destroyed.
+.. [*] Yes, that was the actual key on my server, but the server is already destroyed.