Skip to content

Commit 5a32dde

Browse files
mattmakaimattmakai
committed
updating paas section
1 parent 42df91c commit 5a32dde

File tree

3 files changed

+49
-28
lines changed

3 files changed

+49
-28
lines changed

‎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-16T08:26:09Z</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-17T11:49:31Z</updated></feed>

‎platform-as-a-service.html‎

Lines changed: 28 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -56,20 +56,14 @@ <h1>Platform-as-a-service</h1>
5656
higher-level abstraction for working with computing resources than deploying
5757
an application to a server or IaaS.</p>
5858
<p>A PaaS makes deployment and operations easier because it forces the developer
59-
to conform applications to the PaaS architecture. For example, Heroku looks for
60-
Python's requirements.txt file in the base directory of the repository during
61-
deployment because that is the de facto community standard.</p>
62-
<p><a href="http://www.heroku.com/">Heroku</a>,
63-
<a href="https://developers.google.com/appengine/">Google App Engine</a>,
64-
<a href="https://gondor.io/">Gondor</a>,
65-
<a href="https://www.pythonanywhere.com/">PythonAnywhere</a> and
66-
<a href="https://openshift.redhat.com/community/get-started/python&gt;">OpenShift</a> are
67-
PaaS that support Python web applications. Each one requires varying tradeoffs
68-
to deploy to their respective platforms.</p>
59+
to conform applications to the PaaS architecture. For example, Heroku looks
60+
for Python's requirements.txt file in the base directory of the repository
61+
during deployment because that is the file's de facto community standard
62+
location.</p>
6963
<p><img src="theme/img/servers-versus-paas.png" width="100%" alt="Traditional LAMP server stack versus a Platform-as-a-Service stack" class="technical-diagram" /></p>
70-
<p>If you go the PaaS route, you can skip over the operating system and web
71-
server sections because they are baked into PaaS offerings. PaaS offerings
72-
generally start at the WSGI server layer. </p>
64+
<p>If you go the PaaS route, you can skip configuring an operating system
65+
and web server prebaked into PaaS offerings. PaaS offerings generally start
66+
at the WSGI server layer. </p>
7367
<h2>Platform-as-a-service responsibilities</h2>
7468
<p>Although PaaS offerings simplify setting up and maintaining the servers,
7569
operating system, and web server, developers still have responsibilities for other
@@ -81,6 +75,27 @@ <h2>Platform-as-a-service responsibilities</h2>
8175
as a standard LAMP stack. It's still your responsibility to ensure the web
8276
application framework and your app itself is up to date and secured. See the
8377
<a href="../web-application-security.html">security section</a> for further information.</p>
78+
<h2>Platforms-as-a-service that support Python</h2>
79+
<ul>
80+
<li>
81+
<p><a href="http://www.heroku.com/">Heroku</a></p>
82+
</li>
83+
<li>
84+
<p><a href="https://developers.google.com/appengine/">Google App Engine</a></p>
85+
</li>
86+
<li>
87+
<p><a href="https://gondor.io/">Gondor</a></p>
88+
</li>
89+
<li>
90+
<p><a href="https://www.pythonanywhere.com/">PythonAnywhere</a></p>
91+
</li>
92+
<li>
93+
<p><a href="https://openshift.redhat.com/community/get-started/python&gt;">OpenShift</a></p>
94+
</li>
95+
<li>
96+
<p><a href="https://aws.amazon.com/elasticbeanstalk/">AWS Elastic Beanstalk</a></p>
97+
</li>
98+
</ul>
8499
<h2>Platform-as-a-service resources</h2>
85100
<ul>
86101
<li>

‎source/content/pages/03-deployment/0309-platform-as-a-service.markdown‎

Lines changed: 20 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -31,23 +31,16 @@ higher-level abstraction for working with computing resources than deploying
3131
an application to a server or IaaS.
3232

3333
A PaaS makes deployment and operations easier because it forces the developer
34-
to conform applications to the PaaS architecture. For example, Heroku looks for
35-
Python's requirements.txt file in the base directory of the repository during
36-
deployment because that is the de facto community standard.
37-
38-
[Heroku](http://www.heroku.com/),
39-
[Google App Engine](https://developers.google.com/appengine/),
40-
[Gondor](https://gondor.io/),
41-
[PythonAnywhere](https://www.pythonanywhere.com/) and
42-
[OpenShift](https://openshift.redhat.com/community/get-started/python>) are
43-
PaaS that support Python web applications. Each one requires varying tradeoffs
44-
to deploy to their respective platforms.
34+
to conform applications to the PaaS architecture. For example, Heroku looks
35+
for Python's requirements.txt file in the base directory of the repository
36+
during deployment because that is the file's de facto community standard
37+
location.
4538

4639
<img src="theme/img/servers-versus-paas.png" width="100%" alt="Traditional LAMP server stack versus a Platform-as-a-Service stack" class="technical-diagram" />
4740

48-
If you go the PaaS route, you can skip over the operating system and web
49-
server sections because they are baked into PaaS offerings. PaaS offerings
50-
generally start at the WSGI server layer.
41+
If you go the PaaS route, you can skip configuring an operating system
42+
and web server prebaked into PaaS offerings. PaaS offerings generally start
43+
at the WSGI server layer.
5144

5245

5346
## Platform-as-a-service responsibilities
@@ -64,6 +57,19 @@ application framework and your app itself is up to date and secured. See the
6457
[security section](../web-application-security.html) for further information.
6558

6659

60+
## Platforms-as-a-service that support Python
61+
* [Heroku](http://www.heroku.com/)
62+
63+
* [Google App Engine](https://developers.google.com/appengine/)
64+
65+
* [Gondor](https://gondor.io/)
66+
67+
* [PythonAnywhere](https://www.pythonanywhere.com/)
68+
69+
* [OpenShift](https://openshift.redhat.com/community/get-started/python>)
70+
71+
* [AWS Elastic Beanstalk](https://aws.amazon.com/elasticbeanstalk/)
72+
6773

6874
## Platform-as-a-service resources
6975
* [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).

0 commit comments

Comments
 (0)