Currently in very early development!

To run this project, you can either set up your own machine or use a virtual Ubuntu machine with Vagrant. There are separate instructions for each below:

There is configuration included to run this project inside an Ubuntu virtual machine controlled by Vagrant.

This is especially recommended on Windows. If you go this route, you can skip the Manual Setup section below.

Instead, follow these steps:

1. Install Vagrant and Virtualbox

2. Start the virtual machine.

   This will download a basic Ubuntu image, install some additional software on it, and perform the initial project setup.

   If you are on windows: You should run this command in an Administrator cmd.exe or Powershell.

   $ vagrant up

3. Once your Ubuntu VM is started, you can SSH into it with vagrant ssh. This will use a key-based authentication to log you into the VM.

   You can also log in using any SSH client (e.g. PuTTY), at localhost:2222. The username and password are both vagrant, or you can also configure key-based auth: use vagrant ssh-config to find the private key for accessing the VM.

   When you log in, your terminal will automatically drop into a Python virtualenv and cd to /home/vagrant/uw-message-coding.

You will need to have the following packages installed:

• MySQL 5.5
• Python 2.7 and pip
• virtualenv
• virtualenvwrapper (recommended)
• Node.js
• Bower

Once you have the above prerequisites working, clone this repository to your machine.

Go to the directory where you have cloned the repository and run the setup script, as below:

$ cd uw-message-coding
$ ./setup/scripts/dev_setup.sh

This script will perform the following steps for you:

1. Check that your system has the prerequisites available.
2. Prompt you for database settings. If it can't reach the database, it will give you a snippet of MySQL code needed to create the database with the supplied settings.
3. Create a Python virtual environment. This keeps Python packages needed for this project from interfering with any other packages you already have installed on your system.
4. Creates a .env file in your project directory that sets environment variables for Django, most importantly the database connection settings.
5. Installs python packages, NPM packages, and bower packages (using the fab dependencies command).
6. Runs the database migrations (using fab migrate).

Below is the basic project file structure:

.
├── setup                 # Scripts and templates for setting up running machines
│
├── requirements          # Python dependency lists for pip
│   ├── base.txt         # Requirements for all setups
│   ├── local.txt        # Additional requirements for development setups
│   ├── production.txt   # Additional requirements for production setups
│   └── requirements     # Additional requirements for running tests
│
├── message_coding
│   ├── message_coding     # The Django project files (settings, wsgi.py, main urls.py)
│   ├── base               # Global Django application containing cross-cutting stuff
│   ├── apps               # Site modules
│   │   ├── project       # App for high-level project stuff
│   │   ├── dataset       # App for dataset-related stuff
│   │   └── coding        # App for code schemes and coding stuff
│   │
│   ├── templates          # Global site templates
│   ├── static             # Static files (javascript, css, bower components, etc.)
│   └── manage.py          # The Django management script
│
├── fabfile.py           # Contains common maintenance tasks
└── Vagrantfile          # Defines an Ubuntu VM for testing

Some common tasks you might need to do...

If you want to update your code, database, and dependencies all in one go, just run fab reset_dev. This just runs a series of the commands below in succession.

If someone has added Python packages to one of the files in requirements/*.txt, added Bower packages to bower.json, or added NPM packages to package.json, you can update everything with:

$ fab dependencies

If someone has added migrations, you can run fab migrate to run the migrations and update your development database.

Should you need to reset your database, you can use fab reset_db but be CAREFUL with this.

There is some test data contained in the file setup/test_data.json. After you run fab migrate to create your database structure, you can load the test data:

$ fab load_test_data

This data contains two user profiles. There is an admin user that can access the admin controls, as well as another user who owns a project. Below are their credentials:

Test user: testuser/password
Admin user: admin/admin

If you change the database structure or otherwise need to update the test data file, you can run:

$ fab make_test_data

Change to the project directory and start the development webserver using fab runserver.

The Django webservr will listen on port 8000. If you are running in a Vagrant VM, you can view the site at http://localhost:8080. Otherwise, use http://localhost:8000.

Add new CSS files to message_coding/static/css. To load these in a Django template, add the following:

{% load 'staticfiles' %} {# You will need this at the top of your file #}

{% block css %}
    {{ block.super }}
    <link rel="stylesheet" type="text/css" href="{% static 'css/YOUR_PATH_HERE.css' %}">
{% endblock %}

You can also write your styles in LESS, which will be automatically converted to CSS when it is served to your browser. Just make sure to set type="text/less" in the link tag.

The project includes theme styles in message_coding/static/css/theme that load Bootstrap and allow you to override variables and add additional theme styles.

You can add your own JavaScript files to message_coding/static/css. To load these in a Django template, add the following:

{% load 'staticfiles' %} {# You will need this at the top of your file #}

{% block js %}
   {{ block.super }}
   <script src="{% static 'js/main.js' %}" type="text/javascript"></script>
{% endblock %}

The CoffeeScript compiler is also included, and you can load CoffeeScript in the same way. Just use type="text/coffeescript" in the script tag.

It is recommended to use Bower to install third party JavaScript and CSS packages instead of storing the files in the repo directly.

From the main project folder, you can install Bower packages like this:

$ bower install --save d3

This will download the relevant package into message_coding/static/bower and add the package to the dependencies list in bower.json.

You will then need to add references to the appropriate files in your templates or wherever they need to go.