fullstackpython.github.com/wsgi-servers.html at reStructuredText · gr8linux/fullstackpython.github.com

History

230 lines (219 loc) · 12 KB

Raw

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

222

223

224

225

226

227

228

229

230

<!DOCTYPE html>

<title>Full Stack Python</title>

<!--[if lt IE 9]>

<![endif]-->

<style>

html,

body {

font-size: 18px;

color: #222;

background: #fefefe;

}

body {

padding-top: 30px;

}

.footer {

padding: 20px 0 30px 0;

}

a, a:hover {border-bottom: 1px dotted; color: #444;}

a:hover {text-decoration: none; color: #000;}

.logo-title {font-size: 56px; color: #403072; padding-top: 80px;

font-family: "News Cycle", "Arial Narrow Bold", sans-serif;

font-weight: bold; line-height: 30px; margin-left: 5px;}

.logo-title a, .logo-title a:hover {color: #000; text-decoration: none;

border-bottom: none;}

.logo-title a:hover {color: gray;}

.logo-image {vertical-align: top; border: none;}

a.list-group-item.active {background: #444; border: 1px solid #222;}

a.list-group-item.active:hover {background: #444; border: 1px solid #222;}

#sidebar {margin-top: 30px;}

@media (max-width: 600px) {

.logo-header-section {

margin: 20px 32px 0 0;

}

</style>

var _gaq = _gaq || [];

_gaq.push(['_setAccount', 'UA-19910497-7']);

_gaq.push(['_trackPageview']);

(function() {

var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;

ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';

var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);

})();

</script>

</head>

<body>

</a>

<span class="logo-title"><a href="/">Full Stack Python</a></span>

</div>

<h1>WSGI Servers</h1>

<p>A <a class="reference external" href="http://wsgi.readthedocs.org/en/latest/">Web Server Gateway Interface</a>

(WSGI) server implements the web server side of the WSGI interface for

running Python web applications. The WSGI standard v1.0 is specified in

<a class="reference external" href="http://www.python.org/dev/peps/pep-0333/">PEP 0333</a>. As of September 2010,

WSGI v1.0 is superseded by

<a class="reference external" href="http://www.python.org/dev/peps/pep-3333/">PEP 3333</a>, which defines the

v1.0.1 WSGI standard.</p>

<img alt="WSGI Server <-> Web server <-> Browser" class="technical-diagram" src="theme/img/web-browser-server-wsgi.png" style="width: 100%;" />

<p>A web server's configuration specifies what requests should be passed to

the WSGI server to process. Once a request is processed and generated by the

WSGI server, the response is passed back through the web server and onto

the browser. For example, this Nginx web server's configuration specifics

Nginx should handle static assets (such as images, JavaScript, and CSS

files) under the /static directory and pass all other requests to the WSGI

server running on port 8000:</p>

# this specifies that there is a WSGI server running on port 8000

upstream app_server_djangoapp {

server localhost:8000 fail_timeout=0;

}

# Nginx is set up to run on the standard HTTP port and listen for requests

server {

listen 80;

# nginx should serve up static files and never send to the WSGI server

location /static {

autoindex on;

alias /srv/www/assets;

}

# requests that do not fall under /static are passed on to the WSGI

# server that was specified above running on port 8000

location / {

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

proxy_set_header Host $http_host;

proxy_redirect off;

if (!-f $request_filename) {

proxy_pass http://app_server_djangoapp;

break;

}

</pre>

<p>Note that the above code is a simplified version of a production-ready Nginx

configuration. For real SSL and non-SSL templates, take a look at the

<a class="reference external" href="https://github.com/makaimc/underwear/tree/master/underwear/roles/web/templates">Underwear web server templates</a> on GitHub.</p>

<p>WSGI is by design a simple standard interface for running Python code. As

a web developer you won't need to know much more than</p>

<li>what WSGI stands for (Web Server Gateway Inteface)</li>

<li>that a WSGI container is a separate running process that runs on a

different port than your web server</li>

<li>your web server is configured to pass requests to the WSGI container which

runs your web application, then pass the response (in the form of HTML)

back to the requester</li>

</ul>

<p>If you're using a standard web framework such as Django, Flask, or

Bottle, or almost any other current Python framework, you don't need to worry

about how frameworks implement the application side of the WSGI standard.

Likewise, if you're using a standard WSGI container such as Green Unicorn,

uWSGI, mod_wsgi, or gevent, you can get them running without worrying about

how they implement the WSGI standard.</p>

<p>However, knowing the WSGI standard and how these frameworks and containers

implement WSGI should be on your learning checklist though as you become

a more experienced Python web developer.</p>

<h2>WSGI's Purpose</h2>

<p>Why use WSGI and not just point a web server directly at an application?</p>

<ul>

<li><p class="first"><strong>WSGI gives you flexibility</strong>. Application developers can swap out

web stack components for others. For example, a developer can switch from

Green Unicorn to uWSGI without modifying the application or framework

that implements WSGI.

From <a class="reference external" href="http://www.python.org/dev/peps/pep-3333/">PEP 3333</a>:</p>

<p>The availability and widespread use of such an API in web servers for

Python [...] would separate choice of framework from choice of web

server, freeing users to choose a pairing that suits them, while

freeing framework and server developers to focus on their preferred

area of specialization.</p>

</blockquote>

</li>

<li><p class="first"><strong>WSGI servers promote scaling</strong>. Serving thousands of requests for dynamic

content at once is the domain of WSGI servers, not frameworks.

WSGI servers handle processing requests from the web server and deciding

how to communicate those requests to an application framework's process.

The segregation of responsibilities is important for efficiently scaling

web traffic.</p>

</li>

</ul>

</div>

<h2>WSGI Resources</h2>

and

specifications.</p>

<p><a class="reference external" href="http://gunicorn.org/">Green Unicorn</a>,

<a class="reference external" href="http://code.google.com/p/modwsgi/">mod_wsgi</a>,

<a class="reference external" href="https://github.com/unbit/uwsgi-docs">uWSGI</a>, and

<a class="reference external" href="http://www.gevent.org/">gevent</a> are common WSGI server implementations.</p>

<p>This <a class="reference external" href="http://agiliq.com/blog/2013/07/basics-wsgi/">Basics of WSGI</a> post

contains a simple example of how a WSGI-compatible application works.</p>

<p><a class="reference external" href="http://www.apreche.net/complete-single-server-django-stack-tutorial/">Complete single server Django stack tutorial</a> is thorough and informative for

non-paas hosting choices.</p>

<p>This detailed post entitled

<a class="reference external" href="http://bartek.im/blog/2012/07/08/simplicity-nginx-uwsgi-deployment.html">The Beautiful Simplicity of an nginx and uWSGI Deployments</a>

is great reading for understanding Nginx and uWSGI configurations.</p>

</div>

<br/>

Next read the

<a href="/web-frameworks.html">web frameworks</a> section.

</div>

<a href="/introduction.html" class="list-group-item ">Introduction</a>

<a href="/servers.html" class="list-group-item ">Servers</a>

<a href="/operating-systems.html" class="list-group-item ">Operating Systems</a>

<a href="/web-servers.html" class="list-group-item ">Web Servers</a>

<a href="/platform-as-a-service.html" class="list-group-item ">Platform-as-a-service</a>

<a href="/databases.html" class="list-group-item ">Databases</a>

<a href="/wsgi-servers.html" class="list-group-item active">WSGI Servers</a>

<a href="/web-frameworks.html" class="list-group-item ">Web Frameworks</a>

<a href="/task-queues.html" class="list-group-item ">Task Queues</a>

<a href="/static-content.html" class="list-group-item ">Static Content</a>

<a href="/caching.html" class="list-group-item ">Caching</a>

<a href="/web-browsers.html" class="list-group-item ">Web Browsers</a>

<a href="/web-application-security.html" class="list-group-item ">Web Application Security</a>

<a href="/monitoring.html" class="list-group-item ">Monitoring</a>

<a href="/web-analytics.html" class="list-group-item ">Web Analytics</a>

<a href="/api-integration.html" class="list-group-item ">API Integration</a>

<a href="/source-control.html" class="list-group-item ">Source Control</a>

<a href="/configuration-management.html" class="list-group-item ">Configuration Management</a>

<a href="/dependency-management.html" class="list-group-item ">Application Dependencies</a>

<a href="/no-sql-datastore.html" class="list-group-item ">NoSQL Data Stores</a>

<a href="/about-author.html" class="list-group-item ">About</a>

<a href="/change-log.html" class="list-group-item ">Change Log</a>

</div>

</div></div>

<hr/>

<a href="http://www.mattmakai.com/" class="underline">Matt Makai</a> 2014

</div>

</body>

</html>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

FilesExpand file tree

wsgi-servers.html

Latest commit

History

wsgi-servers.html

File metadata and controls