Nov 11, 2011 - Mac OS X comes with apache 2, to install mod_wsgi just install homebrew and run. Did python3 setup.py install (or python if you're using a different version). Install Apache and mod_wsgi. So you won’t need to set up Apache until you’re ready to deploy Django in production. If you decide to use the latest. How to set up Apache, PHP & MySQL on Mac OS X 10.11 El Capitan & OS X 10.10 Yosemite. If you’re like me and use rewrite rules in an. Download the latest version of the MySQL Disk Image.
Install Apache and modwsgi If you just want to experiment with Django, skip ahead to the next section; Django includes a lightweight web server you can use for testing, so you won’t need to set up Apache until you’re ready to deploy Django in production. If you want to use Django on a production site, use Apache with. Modwsgi is similar to modperl – it embeds Python within Apache and loads Python code into memory when the server starts.
Code stays in memory throughout the life of an Apache process, which leads to significant performance gains over other server arrangements. Make sure you have Apache installed, with the modwsgi module activated.
Django will work with any version of Apache that supports modwsgi. See for information on how to configure modwsgi once you have it installed. If you can’t use modwsgi for some reason, fear not: Django supports many other deployment options. A great second choice is, the predecessor to modwsgi.
Additionally, Django follows the spec, which allows it to run on a variety of server platforms. See the for specific installation instructions for each platform.
Get your database running If you plan to use Django’s database API functionality, you’ll need to make sure a database server is running. Django supports many different database servers and is officially supported with, and (although SQLite doesn’t require a separate server to be running).
In addition to the officially supported databases, there are backends provided by 3rd parties that allow you to use other databases with Django:. The Django versions and ORM features supported by these unofficial backends vary considerably. Queries regarding the specific capabilities of these unofficial backends, along with any support queries, should be directed to the support channels provided by each 3rd party project. In addition to a database backend, you’ll need to make sure your Python database bindings are installed.
Python Mod Wsgi
If you’re using PostgreSQL, you’ll need the package. Django supports both version 1 and 2. (When you configure Django’s database layer, specify either postgresql for version 1 or postgresqlpsycopg2 for version 2.) If you’re on Windows, check out the unofficial. If you’re using MySQL, you’ll need, version 1.2.1p2 or higher.
You will also want to read the database-specific notes for the. If you’re using SQLite and Python 2.4, you’ll need.
Mod Wsgi Express
Use version 2.0.3 or higher. Python 2.5 ships with an SQLite wrapper in the standard library, so you don’t need to install anything extra in that case. Please read the SQLite backend. If you’re using Oracle, you’ll need a copy of, but please read the database-specific notes for the for important information regarding supported versions of both Oracle and cxOracle. If you’re using an unofficial 3rd party backend, please consult the documentation provided for any additional requirements. If you plan to use Django’s manage.py syncdb command to automatically create database tables for your models, you’ll need to ensure that Django has permission to create and alter tables in the database you’re using; if you plan to manually create the tables, you can simply grant Django SELECT, INSERT, UPDATE and DELETE permissions. On some databases, Django will need ALTER TABLE privileges during syncdb but won’t issue ALTER TABLE statements on a table once syncdb has created it.
If you’re using Django’s to test database queries, Django will need permission to create a test database. Remove any old versions of Django If you are upgrading your installation of Django from a previous version, you will need to uninstall the old Django version before installing the new version. If you installed Django using setup.py install, uninstalling is as simple as deleting the django directory from your Python site-packages. If you installed Django from a Python egg, remove the Django.egg file, and remove the reference to the egg in the file named easy-install.pth. This file should also be located in your site-packages directory. Installing an official release. Download the latest release from our.
Untar the downloaded file (e.g. Tar xzvf Django-NNN.tar.gz, where NNN is the version number of the latest release).
If you're using Windows, you can download the command-line tool to do this, or you can use a GUI-based tool such as. Change into the directory created in step 2 (e.g. Cd Django-NNN).
If you're using Linux, Mac OS X or some other flavor of Unix, enter the command sudo python setup.py install at the shell prompt. If you're using Windows, start up a command shell with administrator privileges and run the command setup.py install. These commands will install Django in your Python installation's site-packages directory. Tracking Django development If you decide to use the latest development version of Django, you'll want to pay close attention to, and you'll want to keep an eye on. This will help you stay on top of any new features you might want to use, as well as any changes you'll need to make to your code when updating your copy of Django.
(For stable releases, any necessary changes are documented in the release notes.) If you'd like to be able to update your Django code occasionally with the latest bug fixes and improvements, follow these instructions:. Make sure that you have installed, and that you can run its commands from a shell. (Enter svn help at a shell prompt to test this.). Check out Django's main development branch (the 'trunk') like so. Ln -s ` pwd `/django-trunk/django SITE-PACKAGES-DIR/django (In the above line, change SITE-PACKAGES-DIR to match the location of your system's site-packages directory, as explained in the 'Where are my site-packages stored?' Section above.) Alternatively, you can define your PYTHONPATH environment variable so that it includes the django-trunk directory.
This is perhaps the most convenient solution on Windows systems, which don't support symbolic links. (Environment variables can be defined on Windows systems.).
What about Apache and modpython? If you take the approach of setting PYTHONPATH, you'll need to remember to do the same thing in your Apache configuration once you deploy your production site. Do this by setting PythonPath in your Apache configuration file. More information about deployment is available, of course, in our documentation.
On Unix-like systems, create a symbolic link to the file django-trunk/django/bin/django-admin.py in a directory on your system path, such as /usr/local/bin. Ln -s ` pwd `/django-trunk/django/bin/django-admin.py /usr/local/bin This simply lets you type django-admin.py from within any directory, rather than having to qualify the command with the full path to the file. On Windows systems, the same result can be achieved by copying the file django-trunk/django/bin/django-admin.py to somewhere on your system path, for example C: Python24 Scripts.
You don't have to run python setup.py install, because you've already carried out the equivalent actions in steps 3 and 4. When you want to update your copy of the Django source code, just run the command svn update from within the django-trunk directory. When you do this, Subversion will automatically download any changes.