adding deployment learning checklist

Author: mattmakai

deployment.html

@@ -51,6 +51,23 @@ <h2>Why is deployment necessary?</h2>
 <p>Your web application must live somewhere other than your own desktop or 
 laptop. A production environment is the canonical version of your current 
 application and its associated data.</p>
+<h2>Deployment learning checklist</h2>
+<p><i class="fa fa-check-square-o"></i>
+If you're tight on time look at the 
+<a href="/platform-as-a-service.html">platform-as-a-service (PaaS)</a> options. You can
+deploy a low traffic project web app for free or low cost. You won't have to
+worry about setting up the operating system and web server compared to going
+the traditional server route. In theory you should be able to get your 
+application live on the web sooner with PaaS hosting.</p>
+<p><i class="fa fa-check-square-o"></i>
+<a href="/servers.html">Traditional server options</a> are your best bet for learning
+how the entire Python web stack works. You'll often save money with a virtual
+private server instead of a platform-as-a-service as you scale up.</p>
+<p><i class="fa fa-check-square-o"></i>
+Read about servers, <a href="/operating-systems.html">operating systems</a>, 
+<a href="/web-servers.html">web servers</a> and <a href="/wsgi-servers.html">WSGI servers</a> to get
+a broad picture of what components need to be set up to run a Python web 
+application.</p>
 <h2>Deployment hosting options</h2>
 <p>There are four options for deploying and hosting a web application:</p>
 <ol>

feeds/all.atom.xml

@@ -1,2 +1,2 @@
 <?xml version="1.0" encoding="utf-8"?>
-<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2014-04-28T16:30:37Z</updated></feed>
+<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2014-04-28T16:39:49Z</updated></feed>

source/content/pages/03-deployment/0301-deployment.markdown

@@ -27,6 +27,27 @@ laptop. A production environment is the canonical version of your current
 application and its associated data.
 
 
+## Deployment learning checklist
+<i class="fa fa-check-square-o"></i>
+If you're tight on time look at the 
+[platform-as-a-service (PaaS)](/platform-as-a-service.html) options. You can
+deploy a low traffic project web app for free or low cost. You won't have to
+worry about setting up the operating system and web server compared to going
+the traditional server route. In theory you should be able to get your 
+application live on the web sooner with PaaS hosting.
+
+<i class="fa fa-check-square-o"></i>
+[Traditional server options](/servers.html) are your best bet for learning
+how the entire Python web stack works. You'll often save money with a virtual
+private server instead of a platform-as-a-service as you scale up.
+
+<i class="fa fa-check-square-o"></i>
+Read about servers, [operating systems](/operating-systems.html), 
+[web servers](/web-servers.html) and [WSGI servers](/wsgi-servers.html) to get
+a broad picture of what components need to be set up to run a Python web 
+application.
+
+
 ## Deployment hosting options
 There are four options for deploying and hosting a web application: