Skip to content

Commit 86331c1

Browse files
mattmakaimattmakai
committed
moving location of deployment learning checklist
1 parent dc4e0ba commit 86331c1

File tree

4 files changed

+40
-39
lines changed

4 files changed

+40
-39
lines changed

‎deployment.html‎

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -51,23 +51,6 @@ <h2>Why is deployment necessary?</h2>
5151
<p>Your web application must live somewhere other than your own desktop or
5252
laptop. A production environment is the canonical version of your current
5353
application and its associated data.</p>
54-
<h2>Deployment learning checklist</h2>
55-
<p><i class="fa fa-check-square-o"></i>
56-
If you're tight on time look at the
57-
<a href="/platform-as-a-service.html">platform-as-a-service (PaaS)</a> options. You can
58-
deploy a low traffic project web app for free or low cost. You won't have to
59-
worry about setting up the operating system and web server compared to going
60-
the traditional server route. In theory you should be able to get your
61-
application live on the web sooner with PaaS hosting.</p>
62-
<p><i class="fa fa-check-square-o"></i>
63-
<a href="/servers.html">Traditional server options</a> are your best bet for learning
64-
how the entire Python web stack works. You'll often save money with a virtual
65-
private server instead of a platform-as-a-service as you scale up.</p>
66-
<p><i class="fa fa-check-square-o"></i>
67-
Read about servers, <a href="/operating-systems.html">operating systems</a>,
68-
<a href="/web-servers.html">web servers</a> and <a href="/wsgi-servers.html">WSGI servers</a> to get
69-
a broad picture of what components need to be set up to run a Python web
70-
application.</p>
7154
<h2>Deployment hosting options</h2>
7255
<p>There are four options for deploying and hosting a web application:</p>
7356
<ol>
@@ -91,6 +74,23 @@ <h2>Deployment hosting options</h2>
9174
<p>Note that there are other ways of installing a Python web application through
9275
system-specific package management systems. We won't cover those in this
9376
guide as they are considered advanced deployment techniques.</p>
77+
<h2>Deployment learning checklist</h2>
78+
<p><i class="fa fa-check-square-o"></i>
79+
If you're tight on time look at the
80+
<a href="/platform-as-a-service.html">platform-as-a-service (PaaS)</a> options. You can
81+
deploy a low traffic project web app for free or low cost. You won't have to
82+
worry about setting up the operating system and web server compared to going
83+
the traditional server route. In theory you should be able to get your
84+
application live on the web sooner with PaaS hosting.</p>
85+
<p><i class="fa fa-check-square-o"></i>
86+
<a href="/servers.html">Traditional server options</a> are your best bet for learning
87+
how the entire Python web stack works. You'll often save money with a virtual
88+
private server instead of a platform-as-a-service as you scale up.</p>
89+
<p><i class="fa fa-check-square-o"></i>
90+
Read about servers, <a href="/operating-systems.html">operating systems</a>,
91+
<a href="/web-servers.html">web servers</a> and <a href="/wsgi-servers.html">WSGI servers</a> to get
92+
a broad picture of what components need to be set up to run a Python web
93+
application.</p>
9494
<h2>Deployment resources</h2>
9595
<ul>
9696
<li>

‎feeds/all.atom.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,2 @@
11
<?xml version="1.0" encoding="utf-8"?>
2-
<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-05-11T13:04:45Z</updated></feed>
2+
<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-05-11T13:17:32Z</updated></feed>

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

Lines changed: 21 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -27,27 +27,6 @@ laptop. A production environment is the canonical version of your current
2727
application and its associated data.
2828

2929

30-
## Deployment learning checklist
31-
<i class="fa fa-check-square-o"></i>
32-
If you're tight on time look at the
33-
[platform-as-a-service (PaaS)](/platform-as-a-service.html) options. You can
34-
deploy a low traffic project web app for free or low cost. You won't have to
35-
worry about setting up the operating system and web server compared to going
36-
the traditional server route. In theory you should be able to get your
37-
application live on the web sooner with PaaS hosting.
38-
39-
<i class="fa fa-check-square-o"></i>
40-
[Traditional server options](/servers.html) are your best bet for learning
41-
how the entire Python web stack works. You'll often save money with a virtual
42-
private server instead of a platform-as-a-service as you scale up.
43-
44-
<i class="fa fa-check-square-o"></i>
45-
Read about servers, [operating systems](/operating-systems.html),
46-
[web servers](/web-servers.html) and [WSGI servers](/wsgi-servers.html) to get
47-
a broad picture of what components need to be set up to run a Python web
48-
application.
49-
50-
5130
## Deployment hosting options
5231
There are four options for deploying and hosting a web application:
5332

@@ -69,6 +48,27 @@ system-specific package management systems. We won't cover those in this
6948
guide as they are considered advanced deployment techniques.
7049

7150

51+
## Deployment learning checklist
52+
<i class="fa fa-check-square-o"></i>
53+
If you're tight on time look at the
54+
[platform-as-a-service (PaaS)](/platform-as-a-service.html) options. You can
55+
deploy a low traffic project web app for free or low cost. You won't have to
56+
worry about setting up the operating system and web server compared to going
57+
the traditional server route. In theory you should be able to get your
58+
application live on the web sooner with PaaS hosting.
59+
60+
<i class="fa fa-check-square-o"></i>
61+
[Traditional server options](/servers.html) are your best bet for learning
62+
how the entire Python web stack works. You'll often save money with a virtual
63+
private server instead of a platform-as-a-service as you scale up.
64+
65+
<i class="fa fa-check-square-o"></i>
66+
Read about servers, [operating systems](/operating-systems.html),
67+
[web servers](/web-servers.html) and [WSGI servers](/wsgi-servers.html) to get
68+
a broad picture of what components need to be set up to run a Python web
69+
application.
70+
71+
7272
## Deployment resources
7373
* [Thoughts on web application deployment](http://omniti.com/seeds/thoughts-on-web-application-deployment)
7474
walks through stages of deployment with source control, planning,

‎source/content/pages/08-monitoring-analytics/0805-web-analytics.markdown‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,7 @@ how visitors use the site and why they stay or leave. The key concept to
2828
analytics is *learning* about your users so you can improve your web
2929
application to better suit their needs.
3030

31+
3132
## Web analytics concepts
3233
It's easy to get overwhelmed at both the number of analytics services and
3334
the numerous types of data points collected. Focus on just a handful of

0 commit comments

Comments
 (0)