Skip to content

Commit df3726c

Browse files
mattmakaimattmakai
committed
adding new paas resources
1 parent 1305e1e commit df3726c

4 files changed

Lines changed: 34 additions & 14 deletions

File tree

‎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-02-07T07:34:37Z</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-02-07T10:04:52Z</updated></feed>

‎servers.html‎

Lines changed: 14 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -126,11 +126,11 @@ <h2>Virtualized servers</h2>
126126
the shared server. Choosing virtualized server hosting should be based on
127127
your needs for urgency of service ticket requests and the frequency you
128128
require for ongoing maintenance such as persistent storage backups.</p>
129-
</div>
130129
<div class="section" id="virtualized-servers-resources">
131-
<h2>Virtualized servers resources</h2>
130+
<h3>Virtualized servers resources</h3>
132131
<p><a class="reference external" href="http://blog.redfern.me/choosing-a-low-cost-vps/">Choosing a low cost VPS</a></p>
133132
</div>
133+
</div>
134134
<div class="section" id="infrastructure-as-a-service">
135135
<h2>Infrastructure-as-a-service</h2>
136136
<p>Infrastructure-as-a-service (IaaS) overlaps with virtualized servers
@@ -156,14 +156,14 @@ <h2>Infrastructure-as-a-service</h2>
156156
but you will pay correspondingly more for them. EBS throughput is just
157157
one of many quirks you need to understand before committing to an
158158
IaaS platform.</p>
159-
</div>
160159
<div class="section" id="infrastructure-as-a-service-resources">
161-
<h2>Infrastructure-as-a-service Resources</h2>
160+
<h3>Infrastructure-as-a-service Resources</h3>
162161
<p><a class="reference external" href="http://aws.amazon.com/python/">Amazon Web Services official documentation for Python</a></p>
163162
<p><a class="reference external" href="https://github.com/boto/boto">boto</a> is an amazing Python library for
164163
working with Amazon Web Services</p>
165164
<p><a class="reference external" href="http://docs.rackspace.com/sdks/guide/content/python.html">Rackspace official documentation for Python</a></p>
166165
</div>
166+
</div>
167167
<div class="section" id="platform-as-a-service">
168168
<h2>Platform-as-a-service</h2>
169169
<p>A platform-as-a-service (PaaS) provides infrastructure and a software layer
@@ -183,11 +183,17 @@ <h2>Platform-as-a-service</h2>
183183
<p>If you go the PaaS route, you can skip over the operating system and web
184184
server sections because they are baked into PaaS offerings. PaaS offerings
185185
generally start at the WSGI server layer.</p>
186-
</div>
187186
<div class="section" id="platform-as-a-service-resources">
188-
<h2>Platform-as-a-service resources</h2>
189-
<p><a class="reference external" href="http://rdegges.com/devops-django-part-4-choosing-heroku">Choosing Heroku</a>
190-
(Randall Degges)</p>
187+
<h3>Platform-as-a-service resources</h3>
188+
<p>DevOps Django and Heroku Series by <a class="reference external" href="https://twitter.com/rdegges">Randall Degges</a>:</p>
189+
<ul class="simple">
190+
<li><a class="reference external" href="http://www.rdegges.com/devops-django-part-1-goals/">Part One: Goals</a></li>
191+
<li><a class="reference external" href="http://www.rdegges.com/devops-django-part-2-the-pain-of-deployment/">Part Two: The Pain of Deployment</a></li>
192+
<li><a class="reference external" href="http://www.rdegges.com/devops-django-part-3-the-heroku-way/">Part Three: The Heroku Way</a></li>
193+
<li><a class="reference external" href="http://rdegges.com/devops-django-part-4-choosing-heroku">Part Four: Choosing Heroku</a></li>
194+
</ul>
195+
<p><a class="reference external" href="http://appsembler.com/blog/paas-bakeoff-comparing-stackato-openshift-dotcloud-and-heroku-for-django-hosting-and-deployment/">PaaS bakeoff: Comparing Stackato, OpenShift, Dotcloud and Heroku for Django hosting and deployment</a> by <a class="reference external" href="https://twitter.com/natea">Nate Aune</a></p>
196+
</div>
191197
</div>
192198

193199
<br/>

‎source/content/pages/introduction.rst‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
============
12
Introduction
23
============
34

‎source/content/pages/servers.rst‎

Lines changed: 18 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
=======
12
Servers
23
=======
34

@@ -16,6 +17,7 @@ web application:
1617

1718
4. Platform-as-a-service
1819

20+
----------
1921
Bare metal
2022
----------
2123
The term *bare metal* refers to purchasing the actual hardware and hooking
@@ -44,6 +46,7 @@ smaller case form factors (called "blades") but are correspondingly more
4446
expensive than putting off-the-shelf components together yourself.
4547

4648

49+
-------------------
4750
Virtualized servers
4851
-------------------
4952
Virtual private servers (VPSs) are slices of hardware on top of a larger
@@ -67,11 +70,12 @@ require for ongoing maintenance such as persistent storage backups.
6770

6871

6972
Virtualized servers resources
70-
-----------------------------
73+
=============================
7174
`Choosing a low cost VPS <http://blog.redfern.me/choosing-a-low-cost-vps/>`_
7275

7376

7477

78+
---------------------------
7579
Infrastructure-as-a-service
7680
---------------------------
7781
Infrastructure-as-a-service (IaaS) overlaps with virtualized servers
@@ -103,7 +107,7 @@ IaaS platform.
103107

104108

105109
Infrastructure-as-a-service Resources
106-
-------------------------------------
110+
=====================================
107111
`Amazon Web Services official documentation for Python <http://aws.amazon.com/python/>`_
108112

109113
`boto <https://github.com/boto/boto>`_ is an amazing Python library for
@@ -112,6 +116,7 @@ working with Amazon Web Services
112116
`Rackspace official documentation for Python <http://docs.rackspace.com/sdks/guide/content/python.html>`_
113117

114118

119+
---------------------
115120
Platform-as-a-service
116121
---------------------
117122
A platform-as-a-service (PaaS) provides infrastructure and a software layer
@@ -141,8 +146,16 @@ server sections because they are baked into PaaS offerings. PaaS offerings
141146
generally start at the WSGI server layer.
142147

143148
Platform-as-a-service resources
144-
-------------------------------
145-
`Choosing Heroku <http://rdegges.com/devops-django-part-4-choosing-heroku>`_
146-
(Randall Degges)
149+
===============================
150+
DevOps Django and Heroku Series by `Randall Degges <https://twitter.com/rdegges>`_:
151+
152+
* `Part One: Goals <http://www.rdegges.com/devops-django-part-1-goals/>`_
153+
154+
* `Part Two: The Pain of Deployment <http://www.rdegges.com/devops-django-part-2-the-pain-of-deployment/>`_
155+
156+
* `Part Three: The Heroku Way <http://www.rdegges.com/devops-django-part-3-the-heroku-way/>`_
157+
158+
* `Part Four: Choosing Heroku <http://rdegges.com/devops-django-part-4-choosing-heroku>`_
147159

160+
`PaaS bakeoff: Comparing Stackato, OpenShift, Dotcloud and Heroku for Django hosting and deployment <http://appsembler.com/blog/paas-bakeoff-comparing-stackato-openshift-dotcloud-and-heroku-for-django-hosting-and-deployment/>`_ by `Nate Aune <https://twitter.com/natea>`_
148161

0 commit comments

Comments
 (0)