Omnicommons.org

Omnicommons.org (link) is the main website for the Omni Commons.

Development

The best way to add changes to the website is to fork the main repository (github.com/omnicommons/omnicommons.org) then clone your fork to your local machine and test your changes locally before committing a pull request.

The following text will go over how to get the code on to your local machine and how to configure the machine to display the website, read on!

Fork, Clone, and Configure the Upstream

We assume you already know how to fork a github.com repository, if not please check out github’s article on repo forking

Clone the Repo

Once you have the repository forked you’ll want to clone it to your development machine using the clone command.

Here’s the command that github user dhornbein used:

git clone git@github.com:dhornbein/omnicommons.org.git

Note: This command will be different for you as dhornbein will be replaced by your github.com user name (or where ever you forked the repo)

Configure Remote Upstream

The “remote upstream” is a git remote repo that you pull from for the latest versions of the code. You will add the Omni Common’s omnicommons.org repository as the upstream remote location so you can perform git pull upstream to pull down any changes to the site since you forked it.

First we’ll add the upstream remote, you can copy and paste the line below:

git remote add upstream git@github.com:omnicommons/omnicommons.org.git

Now check that it worked by typing git remote -v to see all remote repos, it should look like this:

origin  git@github.com:dhornbein/omnicommons.org.git (fetch)
origin  git@github.com:dhornbein/omnicommons.org.git (push)
upstream  git@github.com:omnicommons/omnicommons.org.git (fetch)
upstream  git@github.com:omnicommons/omnicommons.org.git (push)

Basically this is saying that the origin of the files is at your (show as dhornbein’s) forked repo and the upstream destination is the Omni Common’s repo.

Setting up Server Side Includes on Localhost

The Omni Commons website uses Server Side Includes (SSI) to pull in head, nav, and footer html from the /includes folder. So we need to set up your local environment to handle this. Much of the following information is taken from linuxtopia.org’s how to guide on apache ssi.

The SSI strings look like this:

<!--#include virtual="/includes/nav.html" -->

Once SSI is enabled this line will be replaced by the content of /includes/nav.html. This allows us to edit the nav once and have those changes appear on all pages with the above snippet.

Enable mod_include

The first thing to do is ensure that your server has the mod_include module installed and enabled.

The following instructions were tested on an Mac OS X (10.9) machine but should work on any Linux machine as well.

First we will examine the Apache Config file httpd.conf typically located