Skip to main content

Running a Django Application on Windows Server 2012 with IIS

This is a first for me since under normal circumstances we run all our Django applications on Linux with Nginx, but we're in the process of developing an application for another department and due to the requirements around this project, we'll be handing the code off to them to deploy. They don't have any experience with Linux or web servers other than IIS, so I recently took up the challenge of figuring out how to run Django applications on Windows Server 2012 with IIS.

Based on the dated or complete lack of information around this I'm assuming it's not something that's very common in the wild, so I thought I'd share what I came up with in case others need to do this.

Creative Commons License
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

Assumptions and Caveats

  1. The operating system is Windows Server 2012 R2, 64-bit. If another variant of the operating system is being used, these instructions may not work properly.
  2. All of the software versions referenced in this document are current as of the date of this blog post.
  3. All actions are performed as the Administrator user, or another user with Administrator rights.
  4. Depending on the audience, some of these steps may seem unnecessarily pedantic. They were originally written to be as foolproof as possible and to make these steps as thorough and complete as they can be. I decided not to simplify or abbreviate anything for this blog post.
  5. The version of Django that is current as of the time of this writing is 1.9.8. If any of the Django-related configuration settings change in the future, the settings outlined in this document may no longer be valid. For example, the details of the call to the Django WSGI handler are specific to this version of Django. They have been different in prior versions of Django, and may need to be updated in the future to reflect changes in Django.
  6. We'll be creating a sample application called foo directly on the server. In real-world circumstances you'll be deploying a completed application to the server, but I thought this was a good way to illustrate the steps and how all the pieces fit together.
  7. If you install things in different locations than outlined here, or put your application in a different location than outlined here, obviously you'll have to adjust paths in configuration settings accordingly.

Prerequisites for Running Django Applications on IIS

If you want to target Windows Server and IIS as the production environment for your Django application, there aren't really any issues of concern other than including the wfastcgi Python package ( in your application.

wfastcgi is maintained by Microsoft as part of Python Tools for Visual Studio (, and provides a file that serves as the entry point of the IIS handler for WSGI applications in Python. It's similar in purpose to a tool like Gunicorn (, with the end result being that requests that come into IIS are handed off to the Python application for processing.

wfastcgi can be installed with pip:
pip install wfastcgi

You’ll also want to add wfastcgi to your Django application's requirements.txt file to make sure it gets installed as part of the deployment of your application.

After installing wfastcgi the file will be in your Python environment's site-packages directory. We’ll point to this file later when we're configuring the IIS handler for Django.

Install Python

  1. Download the latest Windows x86-64 executable installer from
  2. Double-click the Python installer. If you get a security warning at this point, click "Run" to continue.
  3. In the Python Setup dialog that appears, click "Customize Installation"
  4. On the Optional Features step, leave the default settings and click "Next"
  5. On the Advanced Options step, make the following changes:
    1. Check the "Install for all users" box (note that this will also check the "Precompile standard library" box)
    2. Check "Add Python to environment variables"
    3. In the input box below "Customize install location" change the value to the following:
  6. Click "Install"
  7. When the installation is complete, click "Close"

Confirm the Python Installation

  1. Open a new Command Prompt. Note that if you already had a command prompt open you will need to close and reopen it, as the Python installation process added new environment variables and any open command prompts will not have the new environment variables available.
  2. Type python and press Enter. This should open a Python interpreter:
    1. If instead of seeing the Python interpreter you see the error "'python' is not recognized as an internal or external command ..." this likely means the "Add Python to environment variables" box was not checked on the Advanced Options step of the installation process. If this occurs you can uninstall and reinstall Python and make sure to check the "Add Python to environment variables" checkbox, or add the following to the System environment "Path" variable:
  3. Exit the Python interpreter by typing exit() and pressing Enter.
  4. Close the Command Prompt

Install IIS

Even if you already have IIS installed, you may need to go through these steps to install the CGI feature if it wasn't installed as part of the original IIS installation.
  1. Open the Control Panel
  2. In the search box in the top right, type "windows features" (without the quotes)
  3. In the search results under "Programs and Features" click "Turn Windows features on or off." This launches the Add Roles and Features Wizard.
  4. On the "Before you begin" step, click "Next"
  5. On the "Select installation type" leave the "Role-based or feature-based installation" radio button selected and click "Next"
  6. On the "Select destination server" step, leave the current server highlighted and click "Next"
  7. On the "Select server roles" step, scroll to the bottom of the list and check "Web Server (IIS)"
  8. In the "Add features that are required for Web Server (IIS)?" dialog that appears, leave the "Include management tools (if applicable)" checkbox checked and click "Add Features"
  9. On the "Select server roles" step, now that "Web Server (IIS)" is checked, click "Next"
  10. On the "Select features" step, leave the defaults and click "Next"
  11. On the "Web Server Role (IIS)" step, click "Next"
  12. On the "Select role services" step, scroll down to "Application Development," expand that section, and check the "CGI" box. This will also check the "Application Development" checkbox. With "CGI" checked, click "Next."
  13. On the "Confirmation" step, click "Install"
  14. Once the installation completes, click "Close"
  15. Close Server Manager
  16. Close Control Panel

Verify the IIS Installation

  1. Open a web browser on the server
  2. Enter http://localhost in the address bar and press Enter. You should see the default IIS page.
  3. If you don't see the default IIS page:
    1. Open Control Panel
    2. Type "services" in the search box
    3. Under "Administrative Tools" click "View local services"
    4. Scroll to the bottom of the list and ensure you see "World Wide Web Publishing Service" listed, and that the status is "Running"

Create and Configure a Python Virtual Environment for Your Application

Python virtual environments are used to isolate application-specific Python environments from the system-wide Python environment. Even if you will only be running one application on a server, it's good practice to create a virtual environment for your application to keep the virtual environment free from any unanticipated side effects of system updates.
  1. Open a Command Prompt
  2. Navigate to the root of the C: drive:
    cd C:\ [then press Enter]
  3. Create a new directory in which to store your virtual environments:
    mkdir virtualenvs [then press Enter]
  4. Navigate to the newly created virtualenvs directory:
    cd virtualenvs [then press Enter]
  5. Create a new virtual environment. We'll use the name foo for the purposes of illustration. Note that if you change this, you'll have to adjust the rest of the steps in this post accordingly.
    python -m venv foo [then press Enter]

Activate the Virtual Environment and Upgrade pip

With the virtual environment created, the next steps are to activate the virtual environment and update pip, Python's package installer.

First, we'll activate the virtual environment:
  1. Open a Command Prompt
  2. Navigate to the virtual environment's directory:
    cd C:\virtualenvs\foo [then press Enter]
  3. Activate the virtual environment:
    Scripts\activate.bat [then press Enter]
  4. At this point you will see (foo) at the beginning of the command prompt, indicating the virtual environment is active:
    1. Once a virtual environment is active, all Python-related commands such as python, pip, etc. will be executed against the active virtual environment. For example, with the virtual environment active if a package is installed with pip, that package will only be available in the virtual environment, not in the system's global Python environment.
Next, to ensure we don't run into installation or security issues with pip, let's upgrade it:
  1. In the same Command Prompt you opened above, with the virtual environment activated, run the following command:
    python -m pip install --upgrade pip [then press Enter]
    1. If an update for pip is available, it will be downloaded and installed

Install Django and Create a Sample Django Application

Typically, you'll be installing requirements from a requirements.txt file that is part of the codebase for your application, but for the purposes of this installation guide we'll install Django in our virtual environment, both to illustrate the steps involved as well as to ensure the virtual environment is working properly. Then we'll create a sample Django application that we'll use later to configure with IIS.
  1. In the same Command Prompt you opened above, with the virtual environment activated, install Django:
    pip install django [then press Enter]
  2. As outlined in the prerequisites section at the beginning of this document, you'll also need to install wfastcgi in order for IIS to be able to pass requests off to Django:
    pip install wfastcgi [then press Enter]
  3. Navigate to the root of the C: drive:
    cd C:\ [then press Enter]
  4. Create a new directory in which we'll put our application:
    mkdir apps [then press Enter]
  5. Navigate to the newly created apps directory:
    cd apps [then press Enter]
  6. Create a new Django project called foo: startproject foo [then press Enter]
  7. Navigate to the newly created foo project directory:
    cd foo [then press Enter]
  8. Start the Django development server:
    python runserver [then press Enter]
    1. You should see the following output:
  9. In a browser on the server, go to http://localhost:8000
    You should see the following:
  10. Go back to the Command Prompt and press Ctrl-C to stop the Django development server.

Configure IIS to Serve Django Applications

Thus far we've accomplished the following:
  1. Installed Python
  2. Installed IIS with CGI
  3. Created and activated a Python virtual environment
  4. Installed Django and wfastcgi in a Python virtual environment
  5. Created a new Django project
  6. Ran the Django project using the Django development server
With all the underlying infrastructure in place, the last step is to configure IIS to serve Django applications. The Django development server is not designed for production use, so using a production-quality web server such as IIS is mandatory for production applications.

As with previous steps you'll need to adjust accordingly for the actual application you want to deploy, but for the purposes of this documentation we'll configure IIS to serve the test Django application we created in the previous steps.

Configure FastCGI in IIS

  1. Open the IIS Manager by clicking the Windows button, clicking on Administrative Tools, and double-clicking Internet Information Services (IIS) Manager
  2. Click on the name of the server in the list on the left. If you see the following dialog box, check the box "Do not show this message" and click "No." (You can always get to this later if necessary by clicking "Get New Web Platform Components" under "Actions" on the right-hand side of IIS Manager.)
  3. Double-click the "FastCGI Settings" icon
  4. Under "Actions" on the right-hand side click "Add application ..."
  5. In the Add FastCGI Application dialog, in the "Full Path" box, type the path to the Python executable for the application's virtual environment:
  6. In the Arguments input box, type the path to the file in the application's virtual environment:
  7. At this point your settings in the Add FastCGI Application dialog should look like this:
  8. With the Add FastCGI Application dialog box still open, under the "General" section, click on the "Environment Variables" line, then click the gray "..." button that appears next to (Collection) on the right-hand side of the line. This opens the EnvironmentVariables Collection Editor dialog.
  9. In the EnvironmentVariables Collection Editor dialog, click "Add"
  10. In the "Name properties" section on the right, click the input box to the right of "Name," remove the "Name" text that is already in the input box, and enter DJANGO_SETTINGS_MODULE (note that this MUST be entered in ALL CAPS)
  11. Click the input box to the right of "Value" and enter foo.settings
  12. Click "Add" again and enter the following:
    Value: C:\apps\foo
  13. Click "Add" again and enter the following:
    Value: django.core.wsgi.get_wsgi_application()
  14. At this point you will have three environment variables:
    1. NOTE: All of these settings are CASE-SENSITIVE. They must be entered with exactly the case indicated here in order to work.
  15. Click "OK" to close the EnviromentVariables Collection Editor
  16. Click "OK" to close the Add FastCGI Application dialog

Create and Configure a New IIS Web Site

Next we need to create a new web site in IIS for the Django application, and add a Handler Mapping to the newly created web site so that requests coming to the IIS web site are passed off to the Django application for processing.
  1. Open IIS Manager
  2. On the left-hand side under Connections, expand the tree under the server name by clicking on the arrow to the left of the server name
  3. Right-click on the Sites folder and click "Add Website ..."
  4. For the site name enter foo
  5. For the physical path, type the following:
  6. For the purposes of this example configuration, change the Port to 81, since the Default site is running on port 80. For a real-world application you'll likely want to use name-based virtual hosting by adding bindings and run the site on port 80.
  7. You may leave the "Host name" blank. At this point the Add Website dialog should look like this:
  8. Click "OK"
Next, we'll add a FastCGI handler mapping to this site so the requests coming into the site will be processed by the Django application.
  1. In IIS Manager, expand the Sites folder on the left-hand side and click on the foo site
  2. On the right, double-click "Handler Mappings"
  3. On the right, under "Actions," click "Add Module Mapping"
  4. In the "Request path" box enter an asterisk: *
  5. Click the arrow on the right-hand side of the "Module" box and select "FastCgi Module"
    1. NOTE: Make sure to select FastCgi Module, NOT CgiModule
  6. In the "Executable" box, enter the following:
    1. Note that the character after python.exe is a pipe (|), which is entered by pressing Shift-\ on your keyboard
  7. In the "Name" box, enter Django Handler (you can call this whatever you want; it's merely a friendly name for the module mapping)
  8. The Add Module Mapping dialog should now look like this:
  9. Click the "Request Restrictions" button and uncheck the "Invoke handler only if request is mapped to:" checkbox
  10. Click "OK" to close the Request Restrictions dialog
  11. Click "OK" to close the Add Module Mapping dialog
  12. When prompted "Do you want to create a FastCGI application for this executable?" click "No" since we created the application earlier.
    1. Note that you CAN have it create the FastCGI application for you from the module mapping, but the settings seem to be different and the end result isn't fully editable. I also detailed how to create the FastCGI application to be as thorough as possible with all the various pieces involved.
  13. You will now see the Django Handler listed in the Handler Mappings for the foo website:
At this point everything should be working, so verify by loading the application in a browser.
  1. Open a browser on the server
  2. Browse to http://localhost:81
  3. You should see the following:
This is the same result as when we ran the Django test server earlier, but now the requests are being handled by IIS.

Configure Django and IIS to Serve Static Files

Now we have things more or less working but we aren't quite done. If you browse to the Django admin page (http://localhost:81/admin), you'll see something like this:
The reason things look a little strange is because IIS doesn't know where things like the CSS and image files for the Django application are located. In the Django world these assets are referred to as "static files," and we need to perform a couple of additional steps for IIS to be able to serve these files. This isn't an issue during development since Django has a static file server built into it, but in production we'll want IIS to handle serving these files.

How Django handles static files is a bit of a topic in and of itself, so for further information please consult the Django documentation ( In this guide we'll focus on a specific set of steps to get things working without getting into too many of the behind-the-scenes technical details, the different philosophies on where static files can or should be placed, or the various and sundry ways in which this aspect of Django applications can be addressed.

Add a STATIC_ROOT Setting to the Django Settings File

First, your Django application's settings file needs to include a STATIC_ROOT setting, and this setting is not in Django applications by default. The STATIC_ROOT setting is used when Django's collectstatic management command is run to determine where to place the collected static files.

In our sample foo application, we'll tell Django to collect the static files in a static directory located in the same directory as the file. (You can ultimately put your static directory wherever you wish, but this is where we'll be putting it for the purposes of this example.)

To accomplish this, do the following:
  1. Using a plain text editor such as Notepad, or Idle if that was installed when you installed Python, open the file C:\apps\foo\foo\
  2. Scroll to the bottom of the file, or use the find feature of your text editor, and find the STATIC_URL setting
  3. Above the STATIC_URL setting, add the following setting:
    STATIC_ROOT = os.path.abspath(os.path.join(BASE_DIR, 'foo', 'static'))
    1. The placement of the STATIC_ROOT setting in the file doesn't matter, but putting it right next to the STATIC_URL setting is typical and keeps all the settings related to static files in one place.
    2. The STATIC_ROOT setting we're using as our example will put the static files in C:\apps\foo\foo\static
  4. Save the file

Run the collectstatic Management Command

Now that Django knows where to put the static files, we can run the collectstatic management command. This command takes all the static files for your project, including the static files used by the Django admin and other packages in your virtual environment, and puts them under one static directory, the location of which is the STATIC_ROOT setting we added above, so they can be served by the web server.
  1. Open a Command Prompt
  2. Activate the application's virtual environment:
    C:\virtualenvs\foo\Scripts\activate.bat [then press Enter]
  3. Navigate to the application's root directory:
    cd C:\apps\foo [then press Enter]
  4. Run Django's collectstatic management command:
    python collectstatic [then press Enter]
  5. Django will then tell you the directory into which it's going to copy the static files, and ask you to confirm since this process overwrites any existing files in the directory. Type yes at this prompt and press Enter.
  6. The static files will then be copied to the directory indicated by the STATIC_ROOT setting.

Add a static Virtual Directory to the IIS Web Site

Now we have all our static files in one place, but we still haven't told IIS where they're located. We'll accomplish this by adding a static virtual directory to the IIS web site for our application.

Note that the name of the virtual directory in IIS must match the value of the STATIC_URL setting in the Django application's file, absent the beginning and trailing slashes. For our sample application we're using a value of /static/ for the STATIC_URL setting, so the name of the virtual directory in IIS will be static.

Create a virtual directory in IIS as follows:
  1. Open IIS Manager
  2. On the left-hand side under "Connections," expand the server's tree
  3. Expand the "Sites" folder
  4. Expand the foo web site. At this point, things should look like this:
  5. Right-click the foo web site and click "Add Virtual Directory"
  6. In the Add Virtual Directory dialog, enter the following values:
    Alias: static
    Physical path: C:\apps\foo\foo\static
  7. Click "OK." You'll see the static virtual directory appear under the web site.

Configure Handler Mappings for the static Virtual Directory

The last step is to tell IIS which handler to use to serve files out of the static virtual directory. Since at this point our Django Handler is set to serve all files for our application, even with the static virtual directory in place the Django Handler will still be attempting to serve these files.

IIS already has a static file handler active in the web site, but it's down further in the list of handlers than the global Django Handler we configured, so to get IIS to serve the static files under the static virtual directory we'll move the static file handler to the top of the handler list on the static virtual directory.
  1. Open IIS Manager
  2. Expand the server tree
  3. Expand the foo web site
  4. Click on the static virtual directory
  5. Double-click the "Handler Mappings" icon. You'll see the following list of handler mappings:
  6. On the right-hand side under "Actions" click on "View Ordered List ..."
  7. You'll now see a list of the handler mappings in the order in which they're run, with the Django Handler at the top.
  8. Click on the StaticFile handler at the bottom of the list, then click "Move Up" under "Actions" on the right-hand side.
    1. Note at this point you may receive a warning that by moving handlers you are detaching this virtual directory from the inheritance of the parent's handler mappings. This is what we want to do, so if you get this warning click "Yes."
  9. Continue to click "Move Up" until the StaticFile handler is at the top of the list of Handler Mappings.
With the StaticFile handler at the top of the list of Handler Mappings, requests that come into the static directory will be handled by the StaticFile handler as opposed to being processed by the Django Handler, so IIS will serve the static files now.

Confirm that everything is working by going to http://localhost:81/admin in a browser. You should now see the CSS being applied to the page.

Additional Concerns with Static Files

  1. Don't include the directory to which the STATIC_ROOT setting is pointing in your application's code repository; these files should not be tracked and versioned from that location, and the Django development server handles static files for you by serving them directly from their various locations. The collectstatic management command should be run as a normal part of the deployment process for production instances of your application.
  2. For complete information about Django's handling of static files, and production deployment of static files, please refer to the following section of the Django documentation:
At this point your Django application should be playing nicely with IIS.

Additional Information

The information in this section is merely for reference, and to retain some of the research that was performed in the preparation of this guide even though it ultimately may not have been used as part of the final configuration steps.

Resources/Further Reading

Interesting things I came across while preparing this guide, in no particular order:

Additional Avenues of Exploration

Install WFastCGI Gateway for IIS and Python 3.4

Installing WFastCGI for IIS through the IIS Manager is completely optional. It's simply an alternate way of installing Python (in this case Python 3.4 specifically), and also provides the file that is required to configure a handler in IIS for Python applications.

If you perform these steps, Python 3.4 will be installed at the root of the C: drive, and this distribution of Python 3.4 will also place the file in the C:\Python34 directory. You can then leverage this file or copy it into your application's directory to configure the IIS handler.
  1. Open IIS Manager
  2. Click on the server in the list under "Connections" on the left-hand side
  3. At this point you may see a dialog box prompting you to install Microsoft Web Platform:
    1. If you see this dialog box, click "Yes." This will open the download page in a web browser.
    2. If you do not see this box, under "Actions" on the right-hand side of IIS Manager, click on "Get New Web Platform Components." This will open the download page in a web browser.
    3. You will be prompted to launch the Microsoft Web Platform application every time you launch IIS Manager, so if you see this dialog box after you have already installed the Web Platform Installer, feel free to check "Do not show this message" and then click "No."
  4. On the Microsoft Web Platform web page, click the "Free Download" button.
  5. After the download completes, located the downloaded file and double-click to run it. As of the time of this writing the file is called wpilauncher.exe
  6. If you see a Security Warning dialog, click "Run" to run the installer.
  7. After the installation completes, the Web Platform Installer 5.0 application will launch.
  8. In the Web Platform Installer 5.0 application, in the search box on the top right, type "fastcgi" (without the quotes) and press Enter.
  9. In the search results, locate "WFastCGI 2.1 Gateway for IIS and Python 3.4" and click the "Add" button.
  10. At the bottom of the Web Platform Installer application, click "Install."
  11. In the Prerequisites dialog that appears, click "I Accept" to accept the terms of the license.
  12. The WFastCGI extension will be downloaded and installed. When the installation completes, click "Finish" to close the installation dialog, and then click "Exit" to close the Web Platform Installer.
Note that doing installing the WFastCGI Gateway and Python 3.4 in this way does not automatically configure the FastCGI and Handler Mappings in IIS for you. It does install a default Python FastCGI application, but this will not necessarily automatically work with your application, and at a minimum you would still need to add a Handler Mapping for your application.


Hi Matt, thanks for a great and detailed tutorial!!
However, I have encountered a problem when loading the page it returns "scriptProcessor could not be found in application configuration".

After a lot of searching i've found this guide from Microsoft on Azure

Apart from not using virtualenv, the only difference is that they use the pyc version of the wfastcgi instead of py version like what you have... So I changed that and it works ... Could you try again and if it's really because of that, maybe you can help update the tutorial. IIS gave no descriptive error at all, no clue to debug. (Just FYI, I was installing Django 1.9 on Windows Server 2012 R2)
Matt Woodward said…
Thanks for the info -- I wonder if it's a difference between virtualenv on Python 2.x vs. venv on Python 3? Are you using Python 2.x and virtualenv?
jwaynes said…
This is the first 'how to' I've found that actually works! You've done a great job.
Matt Woodward said…
Glad you found it helpful.
Gil Barriga said…
Thank you very much!

This was actually pretty easy and understandable, and it works perfectly. It's quite difficult to find a solution to this.

Thanks again.
Chuck said…
Thank you for this excellent guide.

Note - This worked great on Windows 8.1

Matt Woodward said…
Thanks Chuck! Glad it worked on Windows 8.1.
matt said…
Thanks for this, it really helped me get this up and running. I would like to comment a few of the issues I noticed as I was going through the process.

First off, I was using Windows Server 2008 R2 and can confirm it works on that version as well.

In a few places, I had to change "" to "wfastcgi.exe". I'm not sure if perhaps I am using a different version of wfastcgi, but this was what my virtual environment installed.

I also was having issues with Python 3.5.x but was able to resolve by using Python 3.4.3. I did this because of a statement from this Stack Overflow comment where they are also using Server 2008.

If anyone would like to ask questions, feel free to also tweet at me @The42ndMatt
Matt Woodward said…
Nice -- thanks for the additional info.
Philip Jones said…
Fantastic post on a tricky configuration.

Got this working nicely by following these instructions unmodified for an app using:

* Windows Server 2016
* IIS 11 (I think, from memory).
* Django 1.10.5
* Python 3.6.

Only gotcha I had to overcome - I had enum34 installed in the virtualenv - this broke (silently!). Problem identified by attempting to run the script directly (in the virtual env).

Removing enum34 fixed the issue.

Matt Woodward said…
Thanks for sharing that gotcha! Hopefully that'll save others a lot of troubleshooting time.

Popular posts from this blog

Installing and Configuring NextPVR as a Replacement for Windows Media Center

If you follow me on Google+ you'll know I had a recent rant about Windows Media Center, which after running fine for about a year suddenly decided as of January 29 it was done downloading the program guide and by extension was therefore done recording any TV shows.

I'll spare you more ranting and simply say that none of the suggestions I got (which I appreciate!) worked, and rather than spending more time figuring out why, I decided to try something different.

NextPVR is an awesome free (as in beer, not as in freedom unfortunately ...) PVR application for Windows that with a little bit of tweaking handily replaced Windows Media Center. It can even download guide data, which is apparently something WMC no longer feels like doing.

Background I wound up going down this road in a rather circuitous way. My initial goal for the weekend project was to get Raspbmc running on one of my Raspberry Pis. The latest version of XBMC has PVR functionality so I was anxious to try that out as a …

Setting Up Django On a Raspberry Pi

This past weekend I finally got a chance to set up one of my two Raspberry Pis to use as a Django server so I thought I'd share the steps I went through both to save someone else attempting to do this some time as well as get any feedback in case there are different/better ways to do any of this.

I'm running this from my house (URL forthcoming once I get the real Django app finalized and put on the Raspberry Pi) using I don't cover that aspect of things in this post but I'm happy to write that up as well if people are interested.

General Comments and Assumptions

Using latest Raspbian “wheezy” distro as of 1/19/2013 (’lll be using Nginx ( as the web server/proxy and Gunicorn ( as the WSGI serverI used heavily as I was creating this, so many thanks to the author of that tutorial. If you’re looking for more details on …

The Definitive Guide to CouchDB Authentication and Security

With a bold title like that I suppose I should clarify a bit. I finally got frustrated enough with all the disparate and seemingly incomplete information on this topic to want to gather everything I know about this topic into a single place, both so I have it for my own reference but also in the hopes that it will help others.Since CouchDB is just an HTTP resource and can be secured at that level along the same lines as you'd secure any HTTP resource, I should also point out that I will not be covering things like putting a proxy in front of CouchDB, using SSL with CouchDB, or anything along those lines. This post is strictly limited to how authentication and security work within CouchDB itself.CouchDB security is powerful and granular but frankly it's also a bit quirky and counterintuitive. What I'm outlining here is my understanding of all of this after taking several runs at it, reading everything I could find on the Internet (yes, the whole Internet!), and a great deal…