This README describes how to set up your computer for developing the Pinax implementation of the Kukui Cup. Most of the content can be found in the Pinax documentation and the Django CAS project page.

• Python 2.6 or higher (but not Python 3). On Windows machines, it is recommended that you use the 32 bit version, as using the 64 bit version appears to have issues. Verify that you have it installed by typing python at the command prompt. The interpreter should launch. Close the interpreter by typing exit().
• If on Mac OS X, make sure that the Apple Developer Tools are installed (which is bundled with XCode). You can either get this from your Mac's install DVD or from Apple's site. Note that you need an Apple developer account (which is free) to download from Apple.
• Python Imaging Library (PIL).

• Download the latest official release from the Pinax web site.
• Extract the bundle and using the terminal or a command prompt, change into the new directory.
• Run python scripts/pinax-boot.py <path-to-virtual-env-to-create>. For example, if you want to install to /pinax-env, then type python scripts/pinax-boot.py /pinax-env.
• TROUBLESHOOTING: If you are runninng Python 2.7, you may receive an error along the lines of ImportError: No module named _weakrefset. This is caused by an outdated version of the virtualenv plugin used to create the Pinax environment. You can fix this error by replacing the contents of scripts/pinax-boot.py with the following Gist.
• TROUBLESHOOTING: On Mac OS X Snow Leopard, you may see an issue where the virtual environment fails to install. One way to avoid this is to use the virtualenvwrapper. Follow the steps in the introduction and make a virtualenv for Pinax (i.e. mkvirtualenv pinax-env). You may also want to define $WORKON_HOME to your shell startup file in addition to adding the virtualenv startup script. Then, you can go back to the pinax folder you downloaded and type python scripts/pinax-boot.py $WORKON_HOME/pinax-env to install Pinax into the virtual environment.

• Getting this project requires Git. Find a package for your operating system at the GitHub install wiki.
• It is recommended that you also configure Git so that it handles line endings from Windows users correctly. See Dealing With Line Endings.
• If you only wish to download the source, you can check out using the read-only URL. Type git clone git://github.com/keokilee/makahiki.git to get the source.
• If you wish to commit to the Kukui Cup Pinax project, you will need to create an account at GitHub. Then, you will need to set up your SSH keys and your email settings.
• Once those are set up, send me your Git username so that you can be added as a collaborator.
• When you are added as a collaborator, you should be able to check out the code by using the private url. Type git clone git@github.com:keokilee/makahiki.git to check out the code. This will create the new folder and download the code from the repository.

The following steps are to download additional libraries and upgrade some of the default ones.

• cd into the makahiki folder.
• Start the Pinax virtual environment by typing source <path-to-created-virtual-env>/bin/activate or <path-to-created-virtual-env>\Scripts\activate.bat on Windows. If you used virtualenvwrapper, then you can just use workon <pinax-environment-name>.
• Check if you have pip installed by typing pip help. If it works, great. Otherwise, type easy_install pip to install it.
• Type pip install -r requirements.pip from the application root. This will load the dependencies in requirements.pip.

• cd into the makahiki folder.
• Start the Pinax virtual environment by typing source <path-to-created-virtual-env>/bin/activate or <path-to-created-virtual-env>\Scripts\activate.bat on Windows. If you used virtualenvwrapper, then you can just use workon <pinax-environment-name>.
• Update makahiki_settings.py with the settings related to the competition. Important settings include the CAS authentication server for your organization and your time zone.
• RECOMMENDED: Copy example_settings/local_settings.py.dev to local_settings.py. This file provides additional modules for testing and can be used to override previously defined settings. For example, you can specify a different database in this file.
• Type python manage.py syncdb to create the database.
• It will ask you if you want to create a superuser. Say "no", as this will be done in a later step.
• Run python manage.py migrate to sync the migrations.
• Run python manage.py createsuperuser to create a user.
• IMPORTANT: Use your CAS username as your username. This is so that you can authenticate via the CAS login server.
• Type in a valid email address and any password you like (you probably won't use the password, but emails might be activated later).
• To load some sample data into the application, type ./scripts/load_data.sh. If you are on Windows, you can use scripts\load_data.bat.

• If the virtual environment is not already active, start it by typing source <path-to-created-virtual-env>/bin/activate or <path-to-created-virtual-env>\Scripts\activate.bat on Windows.
• Type python manage.py runserver to start the web server.
• Open a browser and go to http://localhost:8000 to see the website.

The Javascript required to log in to Facebook is included in this application. However, you will need to apply for your own application on Facebook at their Developer Site. Once this is done, it is recommended that you add this to the local_settings.py file. These settings can be added to settings.py, but be aware that a) this file is in public version control, and you don't want others knowing your secret keys and b) subsequent updates may reset the settings.py file.

FACEBOOK_APP_ID = '<APP_ID>'
FACEBOOK_API_KEY = '<API_KEY>'
FACEBOOK_SECRET_KEY = '<SECRET_KEY>'

These can be found in your application's page within the Facebook Developer page.

If you visit http://localhost:8000 and a NoneType exception appears, it is isn't your fault! Django/Pinax has an issue with dumping and loading fixtures that depend on foreign keys. In this case, it is the foreign key that connects the django_generic_flatblocks_genericflatblock table to the django_content_type table. There are several ways of fixing this.

The most straightforward way to fix this is to use SQLite Database Browser to update the tables. Open the database file (by default, it is "dev.db") and browse the data of the "django_generic_flatblocks_genericflatblock" table. Note the values of the website header field (which is of type "title"), the website footer field (type "text"), the website image field (type "image"), and the homepage_content_1 field (type "titleandtext"). Next, browse the contents of the "django_content_type" table. Find the app_label "gblocks" and the names "title", "text", "image", and "titleandtext". What you need to do is execute SQL to update the entries in the "django_generic_flatblocks_genericflatblock" table. An example statement is:

UPDATE django_generic_flatblocks_genericflatblock SET content_type_id=<value in django_content_type> WHERE content_type_id=<value in django_generic_flatblocks_genericflatblock>;

While Django/Pinax has support for running tests, some of the out of the box tests fail (as of Pinax 0.7.1). You can run the tests using python manage.py test. I created my own script to only run my own tests in the system. You can run those tests by typing python runtests.py. These are the same tests that are run by our continuous integration server.

Here are some online Python books that may be helpful when learning the language.

• Dive Into Python
• Learn Python the Hard Way (more geared toward people new to coding)

The following tutorials may be helpful when learning about Django and the various packages used by the system.

• Django Tutorial
• South Tutorial

For information on editing views, consult the Editing Views wiki.