Version 17 (modified by rhand, 15 years ago) ( diff )

--

Third-party distributions of Django

Many third-party distributors are now providing versions of Django integrated with their package-management systems. These can make installation and upgrading much easier for users of Django since the integration includes the ability to automatically install dependencies (like database adapters) that Django requires.

Typically, these packages are based on the latest stable release of Django, so if you want to use the development version of Django you’ll need to follow the instructions for installing the development version from our Subversion repository.

Windows, Linux and Mac OS X

The BitNami Django Stack is a free distribution which includes ready-to-run versions of Apache, MySQL, PostgreSQL, SQLite, Python, Django and required dependencies. It can be deployed using a native installer, as a virtual machine or in the cloud.

FreeBSD

The FreeBSD ports system offers both Django 0.96 (py-django) and a more recent, but not current, version based on Django’s trunk (py-django-devel). These are installed in the normal FreeBSD way; for Django 0.96, for example, type: cd /usr/ports/www/py-django && sudo make install clean.

OpenBSD

There are two options:

  • Install as package: pkg_add py-django
  • Installation over ports system: cd /usr/ports/www/py-django; sudo make; sudo make install

For recent changes http://openports.se/www/py-django

Linux distributions

Archlinux

There are two options available for a repository-controlled installation of django. The first option is the availability of django in the 'extra' repository. The availability of this repository on the system allows for the package to be installed with the magic of 'pacman -S django'. The second option is to install an svnbuild of the package. This package can be found on the Archlinux AUR, and can be easily installed with the yaourt program. Using yaourt as a user with sudo access allows for a relative safe way to install user-made packages. There are multiple other django packages on the AUR. You have for example the django-utils package that can be installed in a similar fashion using yaourt.

Debian

The Debian package is named python-django and can be installed using the following command with root privileges.

aptitude install python-django

all Debian releases, see Debian Reference • Chapter 6 – Debian package management for instructions

Fedora

Package

Gentoo

Package

openSUSE

A Django package is available for openSUSE Linux in the openSUSE Build Service. The current package can be installed by subscribing to the devel:languages:python project and typing 'zypper install python-django'. Alternatively, you can use a one-click-install link.

RPM Based Distributions

from rpmfind.net

SELinux

While the Django documentation recommends starting a Django project outside of the web server's document root (e.g. /var/www), SELinux does not allow web servers such as Apache access outside of their document roots. See also: SELinux - Highly Secured Web Hosting for Python-based Web Applications.

Ubuntu

all Ubuntu releases, see also Ubuntu documentation on "Adding and Removing Software"

Mac OS X

MacPorts

Django can be installed via the MacPorts system:

  • Python 2.4: sudo port install py-django
  • Python 2.5: sudo port install py25-django
  • Python 2.6: sudo port install py26-django

Please note that django-admin.py is renamed according to the Python version you installed it for (django-admin-2.5.py if you installed py25-django).

To enable bash completion install the bash_completion variant (sudo port install py25-django +bash_completion).

To avoid a command not found issue with Snow Leopard 10.6.2 and various other OSX Django installed using MacPorts) here a tip that might help. There might be a $PATH issue. Adding the proper PATH to ~/.Profile: export PATH=/opt/local/bin:opt/local/sbin:/opt/local/lib/python2.4/site-packages/django/bin:$PATH should help. NB Could be that one needs to change the Python version in the PATH.

Note: See TracWiki for help on using the wiki.
Back to Top