Context Navigation

Appendix

-                      v17
+                      v18
 </table>
 }}}
 The Playbook to tell the `server` node to rerun the `nmap` scan and post the results is in `roles/nmap/tasks/map.yml` and looks as follows:
+The Playbook to configure the `server` node is in `server.yml`.  It links to other files.  For example, the code to tell the `server` node to run the `nmap` scan and post the results is in `roles/nmap/tasks/map.yml` and looks as follows:
    {{{
 …
    - name: copy nmap html file to a public place
      command: mv {{ nmap_html_file }} {{ WEB_ROOT }}/{{ nmap_dir }}/nmap.html removes={{ nmap_html_file }}
+[
     }}}
+''Do these commands look like the Ad Hoc commands you came up with in the previous step?''
+Put the above content in a file called `server.yml`.
+''Do these commands look like the Ad Hoc commands from the previous step?''
 Run the playbook with the following command on the local machine:
 …
 }}}
  a. Browse to the server node.  Click on the `nmap` link.
  a. After some of your neighbors have brought up their nodes, run the following command:
+ a. After some of your neighbors have brought up their nodes, run the following command to only do a portion of the `server` configuration:
    {{{
 #!python